Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!caen!newsxfer.itd.umich.edu!gatech!bloom-beacon.mit.edu!news.kei.com!ub!csn!qwerty.fsl.noaa.gov!woody.fsl.noaa.gov!kelly From: kelly@woody.fsl.noaa.gov (Sean Kelly) Subject: Re: Limiting login / idle time Message-ID: <1994Dec19.225831.16004@fsl.noaa.gov> Sender: news@fsl.noaa.gov (USENET News System) Organization: Forecast Systems Laboratory References: <3d2i7o$2ib@news.blkbox.com> Date: Mon, 19 Dec 1994 22:58:31 GMT Lines: 23 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. Xyplex, Annex, and Cisco are some brands that I've used that all have idle timeout features. For login time? Well, you have access to the sources. There are a probably quite a few ways you could do this. Modify getty or login, for example, to register the process group leader with a daemon that kills such processes when time's up. If you'd rather not touch the bin sources, you could also make a special shell for users to whom you want to do this. The shell could fork off an appropriate login shell for the user after setting up to kill off the shell after a certain time. You might want to have it kill all of the users processes---some users might just start an xterm in its own process group to get around your login time checker. I bet others can name at least 10 more possibilities, with at least 10 ways each to get around them. --k