From: Laurence Perkins <lperkins@openeye.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: escape from i3lock
Date: Fri, 12 Jul 2019 16:09:23 +0000 [thread overview]
Message-ID: <eeb006617abe0eede8e9801d969418e25707221b.camel@openeye.net> (raw)
In-Reply-To: <20190712160100.iao7pklozalpdhkp@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Fri, 2019-07-12 at 09:01 -0700, Ian Zimmerman wrote:
> On 2019-07-11 21:28, Nuno Silva wrote:
>
> > vlock -n -a
>
> Does vlock work from an XWindow session? Or would I have to use it
> on
> top of whatever I do to lock the XWindow session -
> xscreensaver/i3lock
> etc?
>
> (I browsed to the vlock README page on github but it doesn't answer
> this
> question.)
>
vlock -a is supposed to lock all virtual consoles. The -n makes it
create a new vt, so it'll work even from within a running X session and
it seems to block the ability to switch back to the X session until the
system is unlocked. But -n also requires root privileges. Might also
want to throw in a -s to temporarily disable alt-sysrq.
This can basically take the place of your current screen locker and
does a better job than even xscreensaver of locking out the system.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-07-12 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 17:03 [gentoo-user] escape from i3lock Ian Zimmerman
2019-07-10 18:44 ` François-Xavier CARTON
2019-07-10 22:48 ` [gentoo-user] " Ian Zimmerman
2019-07-10 23:21 ` artur.tamm.85
2019-07-10 23:46 ` artur.tamm.85
2019-07-11 16:57 ` Ian Zimmerman
2019-07-11 20:47 ` Ian Zimmerman
2019-07-11 21:01 ` artur.tamm.85
2019-07-11 21:10 ` Laurence Perkins
2019-07-12 0:11 ` David Haller
2019-07-12 1:17 ` Laurence Perkins
2019-07-12 8:48 ` Michele Alzetta
2019-07-11 0:43 ` Adam Carter
2019-07-11 16:49 ` Ian Zimmerman
2019-07-11 20:28 ` Nuno Silva
2019-07-12 16:01 ` Ian Zimmerman
2019-07-12 16:05 ` Michele Alzetta
2019-07-12 16:09 ` Laurence Perkins [this message]
2019-07-13 19:11 ` Nuno Silva
2019-07-10 19:23 ` [gentoo-user] " Alec Ten Harmsel
2019-07-10 20:52 ` Neil Bothwick
2019-07-10 21:00 ` Alec Ten Harmsel
2019-07-10 22:45 ` [gentoo-user] " Ian Zimmerman
2019-07-10 21:18 ` [gentoo-user] " Francesco Turco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eeb006617abe0eede8e9801d969418e25707221b.camel@openeye.net \
--to=lperkins@openeye.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox