Date: Fri, 7 Jan 2000 01:40:02 -0800 (PST) From: Jens Schweikhardt <schweikh@noc.dfn.de> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/15832: the w commands can show a bad result on the idle time Message-ID: <200001070940.BAA96650@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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. -- Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) 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?200001070940.BAA96650>