Date: Wed, 23 Sep 1998 12:42:32 +0200 From: Martin Cracauer <cracauer@cons.org> To: "Brian W. Buchanan" <brian@smarter.than.nu>, Mike Smith <mike@smith.net.au> Cc: hackers@FreeBSD.ORG Subject: Re: vty lock Message-ID: <19980923124232.A20756@cons.org> In-Reply-To: <Pine.BSF.4.02A.9809220751220.298-100000@smarter.than.nu>; from Brian W. Buchanan on Tue, Sep 22, 1998 at 07:52:58AM -0700 References: <199809220806.BAA00624@word.smith.net.au> <Pine.BSF.4.02A.9809220751220.298-100000@smarter.than.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
In <Pine.BSF.4.02A.9809220751220.298-100000@smarter.than.nu>, Brian W. Buchanan wrote: > On Tue, 22 Sep 1998, Mike Smith wrote: > > > > I want to write a vty locking program similar in function to Linux's > > > vlock. Anyone have (partial?) code implementing something like this, or > > > have any pointers as to what I'd need to modify in the kernel to > > > facilitate this? > > > > What's wrong with /usr/bin/lock? > > I have to terminate or shell out of whatever I'm running at the moment on > each vty and run it, then enter my password 9 or 10 times when I return to > the console. > > Linux's vlock lets you specify -a to instantly lock ALL vtys, which is the > functionality I'm mainly looking for. Then why don't you add that option to our lock? Simplest solution would be to prevent the console driver from switching consoles, which could be done with a simple ioctl for syscons and pcvt. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980923124232.A20756>