Date: Wed, 26 Apr 2006 15:02:34 -0700 (PDT) From: Bigby Findrake <bigby@ephemeron.org> To: Eric Schuele <e.schuele@computer.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: X11 and virtual consoles.... (startx + vlock) Message-ID: <20060426150134.F71001@home.ephemeron.org> In-Reply-To: <44446828.10704@computer.org> References: <444406E8.2040808@computer.org> <44446828.10704@computer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
1. What about backgrounding startx and then exiting your shell? 2. Have you tried using "lock -np" instead of vlock? On Mon, 17 Apr 2006, Eric Schuele wrote: > Eric Schuele wrote: >> Hello, >> >> [hadn't worn my newbie hat lately... so I thought I'd try it on.] >> >> Is there a way to run X via startx and prevent someone from switching back >> to the console that started it and pressing Ctrl-C, without using >> DontVTSwitch in my xorg.conf file? >> >> I would like to be able to use multiple virtual consoles. But do not like >> the idea of someone switching back to *my* virtual console... killing X and >> having my account available to them. This way I could lock my session via >> xscreensaver, and walk away. Then someone else could login and use the >> machine... just not *my* account. >> >> I had envisioned something like a script that did the following: >> #!/bin/sh >> startx & >> vlock >> >> Yet vlock does not like this at all. I was hoping to background startx... >> and then lock the virtual console. :) > > A little more info.... > So it appears that vlock works if I "manually" background startx from the > console, and then run vlock. but inside the script vlock gets into a loop in > which it thinks it is seeing keystrokes... and repeatedly (quickly) says that > the password is bad, please try again. It does this forever. > > Additionally, the script works just fine for root. It behaves exactly as I > would like. It startx and then locks the console. > > Lastly, I have done a bit more googling, looking for vlock and startx > specifically... and found that (at least in the past) many people have done > it this way with success. I'm not sure what I might be doing wrong here. > > I did turn up one bug that sounds very much like what I am experiencing but > it appears to have been fixed some time ago. I wonder if there is a > regression? Anyone using `startx &; vlock` successfully? > >> >> Is there anything that might accomplish something similar? >> >> Thanks. >> > > > -- > Regards, > Eric > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > /-------------------------------------------------------------------------/ Under deadline pressure for the next week. If you want something, it can wait. Unless it's blind screaming paroxysmally hedonistic ... finger://bigby@ephemeron.org http://www.ephemeron.org/~bigby/ irc://irc.ephemeron.org/#the_pub news://news.ephemeron.org/alt.lemurs /-------------------------------------------------------------------------/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060426150134.F71001>