From owner-freebsd-bugs Sat Aug 17 4:14:55 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6A8937B400; Sat, 17 Aug 2002 04:14:52 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A82143E65; Sat, 17 Aug 2002 04:14:52 -0700 (PDT) (envelope-from schweikh@FreeBSD.org) Received: from freefall.freebsd.org (schweikh@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g7HBEqJU018886; Sat, 17 Aug 2002 04:14:52 -0700 (PDT) (envelope-from schweikh@freefall.freebsd.org) Received: (from schweikh@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g7HBEpaF018882; Sat, 17 Aug 2002 04:14:51 -0700 (PDT) Date: Sat, 17 Aug 2002 04:14:51 -0700 (PDT) From: Jens Schweikhardt Message-Id: <200208171114.g7HBEpaF018882@freefall.freebsd.org> To: pdp@nl.demon.net, schweikh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/25777: atime not updated on exec Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: atime not updated on exec State-Changed-From-To: open->feedback State-Changed-By: schweikh State-Changed-When: Sat Aug 17 04:08:46 PDT 2002 State-Changed-Why: It is not clear if atime needs to be updated upon exec'ing a file. Here's what the current IEEE Std 1003.1-2001 has to say: "File Times Update Each file has three distinct associated time values: st_atime, st_mtime, and st_ctime. The st_atime field is associated with the times that the file data is accessed; st_mtime is associated with the times that the file data is modified; and st_ctime is associated with the times that the file status is changed. These values are returned in the file characteristics structure, as described in . Each function or utility in IEEE Std 1003.1-2001 that reads or writes ^^^^^^^^^^^^^^^ data or changes file status indicates which of the appropriate time-related fields shall be "marked for update". If an implementation of such a function or utility marks for update a time-related field not specified by IEEE Std 1003.1-2001, this shall be documented, except that any changes caused by pathname resolution need not be documented. For the other functions or utilities in IEEE Std 1003.1-2001 (those that are not explicitly required to read or write file data or change file status, but that in some implementations happen to do so), the effect is unspecified. [...]" If we associate "reading" and "writing" with the rwx bits, then to execute you don't need to "read" a file. Bruce (bde), what's your view? http://www.freebsd.org/cgi/query-pr.cgi?pr=25777 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message