Date: Fri, 7 Jan 2000 09:45:54 -0500 (EST) From: Kelly Yancey <kbyanc@posi.net> To: Jens Schweikhardt <schweikh@noc.dfn.de> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/15832: the w commands can show a bad result on the idle time Message-ID: <Pine.BSF.4.05.10001070944240.14781-100000@kronos.alcnet.com> In-Reply-To: <200001070940.BAA96650@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Jan 2000, Jens Schweikhardt wrote: > The following reply was made to PR bin/15832; it has been noted by GNATS. > > From: Jens Schweikhardt <schweikh@noc.dfn.de> > To: freebsd-gnats-submit@FreeBSD.org, admin@ewan.qc.ca > Cc: > Subject: Re: bin/15832: the w commands can show a bad result on the idle time > Date: Fri, 07 Jan 2000 10:32:30 +0100 > > I have discovered the same and tried to investigate > a little (last night at 11pm... so beware). > > The bogus idle time happens on my 3.2-RELEASE system > when I (eg) start a new xterm which needs a new pty, > say /dev/ttypq. If I do not type anything in the new > xterm's shell, /usr/bin/w uses /dev/ttypq's st_atimesec > (as displayed by ls -u /dev/ttypq) > as the last "active" point in time which can well be > beyond the uptime. > > I'm not sure if this is w's fault or if the st_atimesec > of the pty is not properly updated when the pty is used > (opened?). As soon as I run some command in that pty, > everything is okay. > I don't suppose you have the noatime option set for the root filesystem? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10001070944240.14781-100000>