From owner-freebsd-current Thu Aug 2 17:17:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id B96E037B401 for ; Thu, 2 Aug 2001 17:17:47 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 15SSew-0002g4-00; Fri, 3 Aug 2001 02:17:46 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.4/8.11.1) id f7309Pj20198 for freebsd-current@freebsd.org; Fri, 3 Aug 2001 02:09:25 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: What's touching my executables? Date: Fri, 3 Aug 2001 00:09:23 +0000 (UTC) Message-ID: <9kcq3j$jbi$1@kemoauc.mips.inka.de> References: <9kc65b$47n$1@kemoauc.mips.inka.de> <20010802163942.J451@bohr.physics.purdue.edu> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Will Andrews wrote: > Probably the recent change (IIRC) that someone turned running an > executable into a mtime change. That was about _atime_ and the discussion was still going on after I last updated the box. Besides, I verified that simply running an executable does not lead to an mtime change. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message