From owner-freebsd-current Wed Sep 16 14:44:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13658 for freebsd-current-outgoing; Wed, 16 Sep 1998 14:44:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13535; Wed, 16 Sep 1998 14:43:40 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA11432; Wed, 16 Sep 1998 14:43:18 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd011415; Wed Sep 16 14:43:16 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA28315; Wed, 16 Sep 1998 14:43:13 -0700 (MST) From: Terry Lambert Message-Id: <199809162143.OAA28315@usr04.primenet.com> Subject: Re: incorrect output from w To: jmz@FreeBSD.ORG (Jean-Marc Zucconi) Date: Wed, 16 Sep 1998 21:43:12 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199809160215.EAA09875@qix> from "Jean-Marc Zucconi" at Sep 16, 98 04:15:33 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> How can the IDLE time be greater than the uptime? > > > Are you mounting "noatime" or "async"? > > A partition holding the src tree is mounted noatime and a scratch > partition is mounted async. /tmp is on a MFS. All other partitions (/, > /usr, etc...) use default flags (atime, noasync). In general, idle time is calculated from the timestamp on the tty, while uptime is an uptime wall clock. If you have rebooted a chine after a period of inactivity, and a network timesync did not occur before you logged in, then you could see this much drift in that little time. Alternately, if you were not updating the times correctly (the contents of the /dev directory were on an FS where updates were disabled), then you could also see this. Finally, I have assumed that these session are real, and not a wtmp artifact of a system crash. If you did not fix wtmp on boot, you could see "phantom" processes hanging around like this, as well. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message