Control: tags -1 - moreinfo [Jonathan Wiltshire] > Won't this cause problems if the user has switched to make way for > someone else (perhaps it's a shared machine), the second user has > logged out and the first user hasn't unlocked their session to carry > on? If there is unsaved work in that first session, presumably it > will still be lost when the shutdown occurs.
Yes. I have yet to see such use case in a school and in an office, which is the target audience for shutdown-at-night. So in such environments, it is better to not install shutdown-at-night. For the schools I know about, the users log in when they leave the computer and shutdown-at-night work correctly. If you have any idea how to detect if users are logged into X when utmp isn't updated (instead of my current implementation, which detect the X login screen), I am very happy to try a different approach. But at the moment, with display managers and desktop environments failing to update utmp, I am at a loss on how to implement it. :/ > (I do agree your proposed patch is better than the current situation > though.) As far as I can tell, my proposed patch fixes the use cases reported to me, and thus I believe it should be included in stable, unless some better patch solving this and other use cases is available. :) -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org