[16433] in Athena Bugs
dm failed to clean up
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Oct 21 10:56:10 1998
To: bugs@MIT.EDU
Cc: marc@MIT.EDU
In-Reply-To: Your message of "Wed, 21 Oct 1998 04:13:09 EDT."
<199810210813.EAA00332@x15-cruise-basselope.mit.edu>
Date: Wed, 21 Oct 1998 10:56:05 EDT
From: Greg Hudson <ghudson@MIT.EDU>
dm failed to clean up a session on xcb. I collected the syslogs from
dm (and a couple from get_message so we can see where part of Marc's
.xsession ran):
Oct 20 19:19:50 x15-cruise-basselope.mit.edu dm: Starting X, try #1
Oct 20 19:19:50 x15-cruise-basselope.mit.edu dm: Received SIGUSR1; setting x_running.
Oct 20 19:19:50 x15-cruise-basselope.mit.edu dm: Starting console
Oct 20 19:19:50 x15-cruise-basselope.mit.edu dm: Starting xlogin, try #1
Oct 20 19:19:50 x15-cruise-basselope.mit.edu dm: Received SIGUSR1; setting login_running.
Oct 20 19:20:50 x15-cruise-basselope.mit.edu dm: Received SIGALRM.
Oct 20 19:24:50 x15-cruise-basselope.mit.edu last message repeated 4 times
Oct 20 19:25:50 x15-cruise-basselope.mit.edu dm: Received SIGALRM.
Oct 20 19:30:50 x15-cruise-basselope.mit.edu last message repeated 5 times
Oct 20 19:31:50 x15-cruise-basselope.mit.edu dm: Received SIGCHLD for consolepid (28139), status 15
Oct 20 19:31:50 x15-cruise-basselope.mit.edu dm: Starting console
Oct 20 19:31:50 x15-cruise-basselope.mit.edu dm: Received SIGCHLD for consolepid (28348), status 0
Oct 20 19:31:50 x15-cruise-basselope.mit.edu dm: Starting console
Oct 20 19:32:02 x15-cruise-basselope.mit.edu /usr/athena/bin/get_message[28365]: GMS client started...
Oct 20 19:32:02 x15-cruise-basselope.mit.edu /usr/athena/bin/get_message[28365]: GMS not showing.
Oct 20 19:32:02 x15-cruise-basselope.mit.edu dm: Starting console
Oct 20 19:32:50 x15-cruise-basselope.mit.edu dm: Received SIGALRM.
Oct 21 04:04:04 x15-cruise-basselope.mit.edu dm: Received SIGCHLD for loginpid (28140), status 0
Oct 21 08:44:49 x15-cruise-basselope.mit.edu dm: login_running=0, x_running=1, quitting
Oct 21 08:44:50 x15-cruise-basselope.mit.edu dm: Received SIGCHLD for consolepid (28372), status 256
Oct 21 08:44:54 x15-cruise-basselope.mit.edu dm: Received SIGCHLD for xpid (28138), status 0
For reasons related to another bug, Marc SIGTERM'd console at least
once during the login process. Thereafter, dm only got one SIGALRM,
and didn't notice until four hours after Marc logged out (at 4:04am)
that xlogin had died.
I think dmaze has reported this bug before (in the guise of "if you
config_console twice, you can't log out"), but I never had debugging
syslogs from dm about it.
(The fourth "Starting console" syslog is a little bizarre, since dm
didn't log about getting a SIGCHLD for console in the meantime. I
don't know how much we care.)
