And most importantly sending all running processes a hangup signal to allow them to save things that were volatile (like open files) then (if they were still alive) after the “timeout” had expired sending them a -9 signal to kill them, that was in the days of the “init” daemon, i assume systemd does the same thing these days! On 25 Aug 2024, at 15:49, Fulko Hew <fulko.hew@xxxxxxxxx> wrote:
On Sun, 2024-08-25 at 10:17 -0400, Fulko Hew wrote:
> On Fri, Aug 23, 2024 at 1:36 AM Tim via users
> <users@xxxxxxxxxxxxxxxxxxxxxxx>
> wrote:
>
> > Sam Varshavchik wrote:
> > > > I find it highly improbable that there is a "delay reboot for X
> > > > minutes for no reason whatsoever" setting somewhere, that
> > > > simply
> > > > needs to be changed. As Mr. Spock would say: "this is not
> > > > logical".
> >
> > Tim:
> > > Although that pretty much describes what I see on a friend's
> > > iMac.
> > > When you go to shutdown, there's a warning and a countdown before
> > > it
> > > does. With a button to skip waiting and do it now.
> > >
> >
> > For the purposes of clarity, this is MacOS on a Mac. But just
> > pointing
> > out that computer programmers often do things that don't make much
> > sense (the lack of explanation of why you're waiting).
>
>
> Back in time, there was only 'shutdown'. And it had a default
> timeout of 5 minutes to allow the shutdown message to
> be delivered and seen by all the users so that they could
> gracefully end their edit sessions, etc. before the machine
> stopped.
>
> At some point 'halt/halt' and 'reboot' were added.
>
> 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
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.
Then you can simply use 'shutdown now'.
|
--
_______________________________________________
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
