[7285] in testers
xscreensaver process-terminated message
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Wed Jul 20 17:13:44 2005
To: testers@mit.edu
From: Ken Raeburn <raeburn@MIT.EDU>
Date: Wed, 20 Jul 2005 17:13:33 -0400
Message-ID: <tx1irz5rxj6.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
On unlocking my screen, I got this message in my console window:
16:39 xscreensaver: 0: child pid 8655 (<unknown>) terminated with SIGTERM.
I run a zaway process conditional on zwgc already running:
> xrdb -q | egrep -i ^xscreensa
xscreensaver*dpmsEnabled: true
xscreensaver*lock: true
xscreensaver*lockCommand: maybe-zaway
xscreensaver*renew: older
> cat lib/scripts/maybe-zaway
#!/bin/sh
if [ x"$WGFILE" = x ]; then
WGFILE=/tmp/wg.`awk -F: '{if ($1 == "'$USER'")print $3;}' </etc/passwd`
fi
if [ -r $WGFILE ]; then
exec zaway
fi
exit 0
>
... but after running a couple of tests, it appears that the process
in question is an xscreensaver process, child of the main xscreensaver
process, and parent of the zaway process.
I've noticed this seems to be repeatable when the screen is locked via
xscreensaver-button, but I haven't noticed it when I just let the
screen sit idle and the screen saver kicks in.
Ken
