[1343] in testers
Re: Restart cleanup bug
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Dec 5 16:52:09 1990
From: dkk@ATHENA.MIT.EDU
Date: Wed, 5 Dec 90 16:51:36 -0500
To: Richard Basch <probe@MIT.EDU>
Cc: testers@MIT.EDU
In-Reply-To: Richard Basch's message of Tue, 4 Dec 90 18:19:49 -0500,
> Perhaps the machine was in the middle of a "reactivate" at the
> moment.
Sorry my message wasn't a little clearer. Again, the quoted command
and output:
alecto# ls -l /etc/nologin ; cat /etc/nologin ; last -1
-rw-r--r-- 1 root 62 Dec 4 01:18 /etc/nologin
This machine is down for cleanup; try again in a few seconds.
root console Tue Dec 4 01:18 - 01:39 (00:20)
Note the date on /etc/nologin is 01:18. I had logged out about 20
minutes later, but /etc/nologin was still present. There were no
logins other than the one listed above. When I sent mail to testers
hours later, /etc/nologin was still present. If I hadn't rm'd the
file, /etc/nologin would have still been present long afterwards.
If this problem isn't corrected soon (or already, with 7.2D), is there
any reason that "reactivate" shouldn't recognize its own /etc/nologin
file? Otherwise, a workstation can never recover from this state
without a reboot or manual intervention as root.
