Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!spool.mu.edu!howland.reston.ans.net!news.sprintlink.net!news.indirect.com!wes From: wes@indirect.com (Barnacle Wes) Subject: Re: Limiting login / idle time Message-ID: <D1397t.86L@indirect.com> Sender: usenet@indirect.com (System Operator) Organization: the Briney (notso) Deep Date: Tue, 20 Dec 1994 02:50:16 GMT References: <3d2i7o$2ib@news.blkbox.com> <1994Dec19.225831.16004@fsl.noaa.gov> X-Newsreader: TIN [version 1.2.1 [BP] PL2.1] Lines: 24 Sean Kelly (kelly@woody.fsl.noaa.gov) wrote: : In article <3d2i7o$2ib@news.blkbox.com>, Jeff Hupp <jhupp@Gensys.com> wrote: : > How do you limit login and idle time for dialup ttys? : Idle timeout is probably better left to a terminal server... : For login time? Well, you have access to the sources... : I bet others can name at least 10 more possibilities, with at least 10 : ways each to get around them. Actually, I wrote a commercial program that does this last year. It's been incorporated into another larger (i.e. more expensive) product and not released yet. This product even did a limited version of idle-cpu detection, like "if this user hasn't used at least 50 ms of cpu time in the last 30 minutes, throw him/her off." This is an interesting problem, and difficult to do well, especially if you throw in X "sessions", which are *not* well-defined with regards to the kernel. RSVP if you want more details; I'm glad to discuss strategies but don't want to re-write the code. Been there, done that. Skied it, surfed it, sailed it, Dew'ed it. ;^0 Wes Peters