-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document how to switch to single-user mode #24928
Conversation
If people are doubting this, their memory, or mine, they are welcome to review the sysvinit https://manpages.debian.org/bullseye/sysvinit-core/shutdown.8.en.html which explicitly says:
|
6b5d06d
to
b8b13e4
Compare
fd35c2e
to
b34fda2
Compare
Before Debian switched to systemd, `shutdown now` would reset the system into single user mode, doing roughly the equivalent of `telinit 1`. Now, systemd's `shutdown` command does not behave that way; it defaults to `poweroff` which might be confusing for users (like me) used to the previous method. Because I don't use the command often, I keep being stumped by this behavior, and every time I look at the `shutdown(1)` manpage, I don't understand why I can't find what I am looking for. This patch should make sure that people like me find their way back to some sort of reason. Maybe the *proper* way to fix this would be to restore the more classic behavior, but I'm definitely not going to climb that hill. Besides, I clearly remember the time I found out about the `shutdown` command and was *really* confused when it brought me back to a command-line prompt. That was really counter-intuitive and I find that change to actually be a good thing. So I'm not proposing to change this behavior, merely document it better. I originally added this to the `-P` option but it was suggested adding a new `COMPATIBILITY` section instead, where other such issues could be added. The `COMPATIBILITY` section is not actually officially documented. `man(1)` talks about a `CONFORMING TO` section, but `shutdown(1)` is not POSIX (`shutdown(2)` is, of course), so there's no actual standard on how this should work. The other option I considered was to add a `BUGS` section, but that seemed to inflammatory, and definitely counter-productive.
Before Debian switched to systemd,
shutdown nowwould reset the system intosingle user mode, doing roughly the equivalent of
telinit 1.Now, systemd's
shutdowncommand does not behave that way; it defaults topoweroffwhich might be confusing for users (like me) used to the previousmethod.
Because I don't use the command often, I keep being stumped by this behavior,
and every time I look at the
shutdown(1)manpage, I don't understand why Ican't find what I am looking for. This patch should make sure that people like
me find their way back to some sort of reason.
Maybe the proper way to fix this would be to restore the more classic
behavior, but I'm definitely not going to climb that hill. Besides, I clearly
remember the time I found out about the
shutdowncommand and was reallyconfused when it brought me back to a command-line prompt. That was really
counter-intuitive and I find that change to actually be a good thing. So I'm
not proposing to change this behavior, merely document it better.
I originally added this to the
-Poption but it was suggested adding a newCOMPATIBILITYsection instead, where other such issues could be added.The
COMPATIBILITYsection is not actually officially documented.man(1)talks about a
CONFORMING TOsection, butshutdown(1)is notPOSIX (
shutdown(2)is, of course), so there's no actual standard on how thisshould work.
The other option I considered was to add a
BUGSsection, but that seemed toinflammatory, and definitely counter-productive.