Ticket #819 (closed defect: fixed)
/etc/nologin needs to stop being a symlink
| Reported by: | geofft | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | Precise Beta |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
A while back I had this brilliant idea that /etc/nologin on cluster machines would be a symlink to /var/run/debathena-reactivate/something or so. It wasn't as brilliant as you would hope. In particular, programs like to delete /etc/nologin...
I think this is still the case, and if so it needs to be fixed.
Change History
comment:2 Changed 14 years ago by jdreed
Also, should we only do this on -cluster, or what? If we choose to nologin a -workstation machine during auto-update, we'll need to be careful we don't scribble over an existing nologin file, thus opening up logins after an update which the sysadmin might not have wanted.
comment:3 Changed 13 years ago by jdreed
- Status changed from new to committed
- Milestone changed from The Distant Future to Precise Beta
Commited in 2.0.31 (UNRELEASED) in r25495.
Note: See
TracTickets for help on using
tickets.
We need to ensure /etc/nologin is cleaned up on boot and upon termination (both successful and unsuccessful) from auto-update. If an update fails catastrophically (at, for example), or if a user decides to reboot a workstation while it's updating, then /etc/nologin shouldn't persist, otherwise logins will be disabled until the next update (or possibly until forever, if auto-update breaks hard enough).