From owner-freebsd-current Fri Sep 25 15:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28182 for freebsd-current-outgoing; Fri, 25 Sep 1998 15:40:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from starkreality.com (fire.starkreality.com [208.24.48.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28141 for ; Fri, 25 Sep 1998 15:40:01 -0700 (PDT) (envelope-from caesar@starkreality.com) Received: from temp17 ([12.19.232.72]) by starkreality.com (8.9.1/8.9.1) with SMTP id RAA08003 for ; Fri, 25 Sep 1998 17:39:47 -0500 (CDT) Message-Id: <199809252239.RAA08003@starkreality.com> X-Sender: caesar@fire.starkreality.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.52 (Beta) Date: Fri, 25 Sep 1998 18:39:18 -0400 To: freebsd-current@FreeBSD.ORG From: "William S. Duncanson" Subject: Problems with idle time Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a bizarre problem that I've been noticing for the past couple of weeks. If a user is erratically disconnected, and their sessions sticks around, the idle-time will jump to an unrealistic number. An error in the wtmp code somewhere perhaps? Here's an example: fire /home/caesar $ w 5:34PM up 9:04, 4 users, load averages: 0.08, 0.04, 0.01 USER TTY FROM LOGIN@ IDLE WHAT caesar p1 12.19.232.65 8:39AM 48 -bash (bash) caesar p2 12.19.232.65 2:50PM 2:33 tin caesar p3 12.19.232.65 5:21PM 2days -bash (bash) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ caesar p4 12.19.232.72 5:34PM - w World was installed this morning, from sources cvsuped AM on the 23rd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message