From owner-freebsd-bugs Sat Jan 25 2:40: 6 2003 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 3B3A137B405 for ; Sat, 25 Jan 2003 02:40:05 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E124F43F1E for ; Sat, 25 Jan 2003 02:40:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0PAe4NS034896 for ; Sat, 25 Jan 2003 02:40:04 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0PAe43M034895; Sat, 25 Jan 2003 02:40:04 -0800 (PST) Date: Sat, 25 Jan 2003 02:40:04 -0800 (PST) Message-Id: <200301251040.h0PAe43M034895@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: buhrow@lothlorien.nfbcal.org Subject: Re: kern/25777: atime not updated on exec Reply-To: buhrow@lothlorien.nfbcal.org 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 The following reply was made to PR kern/25777; it has been noted by GNATS. From: buhrow@lothlorien.nfbcal.org To: freebsd-gnats-submit@FreeBSD.org, pdp@nl.demon.net Cc: buhrow@lothlorien.nfbcal.org Subject: Re: kern/25777: atime not updated on exec Date: Sat, 25 Jan 2003 02:38:14 -0800 (PST) Hello. Having not read these patches thoroughly, it's unclear to me if they cause the atime field to be updated if a segment of an executable is paged-in during program execution, i.e. when new data needs to be paged in for a daemon process, but historical behavior on FreeBSD, as well as other BSDish systems suggests that it should. Also, I note that the bug is still present in FreeBSD-4.7 stable as of December 2002. It would be very nice if someone could make this work in FreeBSD 4.x again, or, at the very least, correct the problem in FreeBSD-5.1. -thanks -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message