Ticket #816 (closed defect: fixed)

Opened 11 years ago

Last modified 10 years ago

debathena-nologin-monitor may not reliably work

Reported by: jdreed Owned by: jdreed
Priority: normal Milestone: Natty Alpha
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

I kicked off an update on m56-129-16 today via at(1) and no message appeared on the login screen. The update definitely occurred, as verified by the disk thrashing, and the update log timestamps.

However this machine had other issues, in that the GNOME theme was incorrect on the login screen (it displayed the computer icon instead of the ubuntu icon, and displayed the red power button instead of the gray one. We should do a bit more testing and verify that nologin-monitor actually works on lucid (since it was initially deployed on Jaunty and I haven't tested it since).

Change History

comment:1 Changed 11 years ago by jdreed

  • Owner set to jdreed
  • Status changed from new to accepted

Right, so, uh, this has never worked, because /etc/nologin is a symlink, and we only check for created and deleted events. It's unclear if a "changed" event is emitted when the target of a symlink either appears or vanishes, but I don't think it is. So, argh. We should probably ship this only in cluster and monitor /var/run/athena-nologin instead.
(We shouldn't block logins on -workstation while auto-update is running, right? or should we?)

comment:2 Changed 11 years ago by jdreed

  • Status changed from accepted to development

Please test this, I'd

(We shouldn't block logins on -workstation while auto-update is running, right? or should we?)

Bueller?

comment:3 Changed 11 years ago by jdreed

er, that should say "Please test this, i'd like to push it out soon, because we're actively losing when people reboot workstations during an update since they can't log in"

comment:4 Changed 10 years ago by jdreed

  • Status changed from development to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.