Fulko Hew: > > But 'shutdown' provided all the housekeeping work such as: > > - disabling logins > > - sending out messages to users screen warning them of the impending > > doom > > - providing grace time > > - unmounted file systems > > - killed the system Patrick O'Callaghan: > Same here. However these are reasonable measures on a multi-user > system. On a single-user desktop they just get in the way, especially > with journal-based filesystems. Things really oughta order unmounts, unmounts should happen pretty quickly, be flagged as done, and the progress of shutting down be monitored. Not, order unmounts, wait some time, and assume it worked. Likewise for various other shutdowns. Things may have terminated almost instantly without issues, things may have jammed and it still wouldn't have waited long enough. If something sticks you really ought to be prompted about it. If you don't have network mounts, databases running, mail servers currently dealing with a queue, etc, I see no excuses for prolonged shutdowns. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
