On most of my machines, "reboot" entered as root causes the machine to
shutdown and then reboot, as I expect it should. But on one machine,
the machine does not restart. In the process of trying to understand
why this might be, I discovered that reboot is not an actual command:
# pwd
/root
# which reboot
/usr/sbin/reboot
# ls -l /usr/sbin/reboot
lrwxrwxrwx 1 root root 13 2025-07-10 20:42 /usr/sbin/reboot -> ../bin/reboot
# ls -l /bin/reboot
lrwxrwxrwx 1 root root 16 2026-02-06 16:00 /bin/reboot -> ../bin/systemctl
# ls -l /bin/systemctl
-rwxr-xr-x 1 root root 322584 2026-02-06 16:00 /bin/systemctl
This seems to say that entering "reboot" invokes "systemctl"
with no arguments. But the man page for systemctl implies that a
COMMAND argument is required and gives no hint what happens if none
is given. In fact, running "systemctl" with no arguments from the
command line acts like I had entered "systemctl list-units".
BTW, "shutdown" also traces to "systemctl". But on the misbehaving
machine, "shutdown -r" actually works as expected.
So how is it that entering "reboot" results in a reboot, at least on
most of my machines? And how can I discover why it leaves the machine
powered down on one of them?
All of these machines are running Fedora 43 x86_64 regularly upgraded.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
[email protected] [email protected]
"Any idiot can face a crisis;
it's the day-to-day living that wears you out." -- Anton Chekhov
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
