From owner-freebsd-isp Wed Sep 10 15:43:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA03488 for isp-outgoing; Wed, 10 Sep 1997 15:43:05 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA03481 for ; Wed, 10 Sep 1997 15:43:00 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA26296; Thu, 11 Sep 1997 08:42:34 +1000 (EST) Date: Thu, 11 Sep 1997 08:42:33 +1000 (EST) From: "Daniel O'Callaghan" To: Robert Ricci cc: FreeBSD-isp@FreeBSD.ORG Subject: Re: Limiting users connect time (+ another little questi In-Reply-To: <199709101649.KAA15010@ns2.theonlynet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Actually, it seems to have moved to http://www.darkwing.com/idled/ . > > Two questions for people already using idled: When I do a `w`, it > reports an idle time equal to the time the user has been logged in, > not the time they've really been idle. In fact, with some Macs, it > reports no idle time at all. idle time is idle time of the userland process, which is only used for BSD compression. Kernel pppd can be active entirely in the kernel, and therefore appear to be idle. I have a program 'ifidled' which looks at the packets received on the user's pppX interface. I'll put it up for ftp this afternoon. Danny