From owner-freebsd-current Sun Jan 12 11:53:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA17234 for current-outgoing; Sun, 12 Jan 1997 11:53:54 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA17208 for ; Sun, 12 Jan 1997 11:53:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA26071; Sun, 12 Jan 1997 12:41:45 -0700 From: Terry Lambert Message-Id: <199701121941.MAA26071@phaeton.artisoft.com> Subject: Re: patch to lock(1) To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 12 Jan 1997 12:41:45 -0700 (MST) Cc: regnauld@tetard.glou.eu.org, freebsd-current@FreeBSD.ORG In-Reply-To: from "J Wunsch" at Jan 12, 97 07:01:02 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > 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. > > I tend to say that this is rather a kind of `local hack' without much > general demand for it. Plus you could just type in the root password to unlock the thing... Heh... now where's my private password logging version of "lock"... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.