From owner-freebsd-current Fri Jan 17 08:15:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA10954 for current-outgoing; Fri, 17 Jan 1997 08:15:29 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA10938 for ; Fri, 17 Jan 1997 08:15:15 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id AAA17432 for freebsd-current@freebsd.org; Sat, 18 Jan 1997 00:14:55 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 17 Jan 1997 16:14:54 GMT From: peter@spinner.DIALix.COM (Peter Wemm) Message-ID: <853517694.662612@haywire.DIALix.COM> Organization: DIALix Internet Services References: Subject: Re: patch to lock(1) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , j@uriah.heep.sax.de (J Wunsch) writes: > As Philippe Regnauld wrote: > >> I got sick of people locking terminals for 3 hours and not coming back :-) >> >> I made two simple patches to lock(1) so that the user cannot lock the >> terminal more than 1 hour unless he's root. > > That's not the right way to go. If you want such a functionality, you > also need to make the max value configurable in some way, e.g. via a > file in /etc. Perhaps add an attribute to /etc/login.conf now that we have it.. -Peter