From owner-freebsd-bugs Fri Jan 7 9:30: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AAFB8157DC for ; Fri, 7 Jan 2000 09:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA99887; Fri, 7 Jan 2000 09:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 7 Jan 2000 09:30:03 -0800 (PST) Message-Id: <200001071730.JAA99887@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kelly Yancey Subject: Re: bin/15832: the w commands can show a bad result on the idle time Reply-To: Kelly Yancey Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15832; it has been noted by GNATS. From: Kelly Yancey To: Jens Schweikhardt Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/15832: the w commands can show a bad result on the idle time Date: Fri, 7 Jan 2000 12:28:56 -0500 (EST) > # > # I don't suppose you have the noatime option set for the root filesystem? > > Good point, I'll verify this as soon as I get home. > > But why is it that the st_atime seems to be changed when I type something? > In-core copy of the respective struct stat? > Good point. Scratch that. If the file system was mounted with noatime then it shouldn't be updated at all. The correct answer is that stat(2) documents that the atime field is only updated by the mknod(2), utimes(2) and read(2) system calls. Open(2) doesn't touch atime. What you are seeing is documented behaviour, even if it isn't intuitive. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message