Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site pucc-k Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!CS-Mordred!Pucc-H:Pucc-I:Pucc-K:rsk From: rsk@pucc-k (Wombat) Newsgroups: net.sources Subject: Re: Re: Automatic Logout Process Message-ID: <1221@pucc-k> Date: Thu, 15-Aug-85 11:08:32 EDT Article-I.D.: pucc-k.1221 Posted: Thu Aug 15 11:08:32 1985 Date-Received: Sun, 18-Aug-85 01:40:38 EDT References: <6@andromeda.UUCP> <264@sesame.UUCP> <958@rayssd.UUCP> <165@laidbak.UUCP> <38@cbnap.UUCP> Reply-To: rsk@pucc-k.UUCP (Wombat) Organization: Purdue University Lines: 19 In article <38@cbnap.UUCP> whp@cbnap.UUCP (W. H. Pollock x4575 3S235) writes: > >You must be using csh or some non standard shell, because the Bourne shell >(and the Korn shell too) already have a timeout mechanism! I'm using a >SVR2.0V1 unix ... >but I'm sure the changes were in previous releases ... > >Upon invocation, sh checks to see if the environment variable "TMOUT" is set; >if so, this over-rides the default defined in timeout.h. On some shells >I've used, the variable was called "TIMEOUT". Besides the unwarranted backhand slap at what most folks consider to be the standard shell for Berkeley systems, you are also guilty of sloppy thinking. If you will re-read the previous discussion, you will note that the mechanisms provided by sh/ksh, which allow the user to override any previously specified timeout value, are grossly insufficient for the expressed purpose--enforced logout after a set idle period. -- Rich Kulawiec rsk@{pur-ee,purdue}.uucp, rsk@purdue-asc.csnet rsk@purdue-asc.arpa or rsk@asc.purdue.edu