I am trying to enforce xautolock[0] on my X clients, and I did so by cat <<EOF > /etc/X11/Xsession.d/70xautolock export PID=$$ (xautolock -secure; kill $PID) & EOF according to my theory, this should start a subshell and xautolock in it. As soon as xautolock exits, this should kill the Xsession process, which should take the entire X session with it, effectively logging the user out. However, it's not working. I can kill xautolock and stay in X. My first thought was that this is related to `set -e`, which would prevent the subshell to ever execute kill, since the killing of xautolock would be a failure. However, shell options do not propagate to subshells, so the xautolock-containing shell is +e by default. Can you figure out why this is failing? Thanks for any hints! -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
Attachment:
signature.asc
Description: Digital signature