Date: Wed, 6 Dec 2000 22:37:39 -0600 (CST) From: David Talkington <dtalk@prairienet.org> To: David Raistrick <keen@damoe.wireless-isp.net> Cc: Nick Slager <nicks@albury.net.au>, Phil C <mongo@elephantitis.org>, freebsd-questions@FreeBSD.ORG Subject: Re: xlock... Message-ID: <Pine.LNX.4.21.0012062236240.827-100000@sherman.spotnet.org> In-Reply-To: <Pine.BSF.4.21.0012062317090.30371-100000@damoe.wireless-isp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>If someone had xlock running and there were no option but a powercyle to >regain access to the workstation....it would be a bad thing. Oh, you mean like, um, the Windows 95 "locking" screensaver, for instance? (Category: "What were they thinking?" =) -d > >to quote: > >XLOCK(1) XLOCK(1) > > >NAME > xlock - Locks the local X display until a password is > entered. >.... > > >NOTE ON ETIQUETTE > Xlock should not be used on public terminals when there is > a high demand for them. > > If you find a public terminal that has been locked by > another user and there are no other terminals available, > and the terminal appears to have been left idle for a > while (normally more than 15 minutes), it is fair to try > to reset the session in some manner. > >... > > -/+allowroot > The allowroot option allows the root password to > unlock the server as well as the user who started > xlock. May not be able to turn this on and off > depending on your system and how xlock was config- > ured. >... > > > >....david > > >-- >David Raistrick Digital Wireless Communications >davidr@dwcinet.com > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0012062236240.827-100000>