I've recently built a VM against jessie, and just for the heck of it, I left it with the default systemd-based configuration. When I log in to the console as root and try to shut down, I get the following: ======== # shutdown -h -t 0 Broadcast message from root@hostname (Fri 2015-09-11 14:08:29 EDT): The system is going down for power off at Fri 2015-09-11 14:09:29 EDT! ======== I.e., even though I specified a shutdown delay of zero seconds (meaning to shut down immediately), the shutdown is being delayed by 60 seconds. What I expected instead was a response including the line ======== The system is going down for power off NOW! ======== and an immediate shutdown (without even enough delay to log root out via Ctrl-D), which is what I get on my other systems, where systemd is not the active init system. Google has not been helpful in trying to figure out why this might be happening; there are plenty of hits explaining how to make systemd inhibit shutdown or add a delay or the like, and a few hits related to Debian bug 635777 (which seems to be about a delay after the shutdown has actually begun, not about a delay in initiating the shutdown), but no real useful hints. Grepping recursively and case-insensitively through /etc/systemd for 'shut' and '60' (separately) produces only two hits, neither of which seems relevant. Any idea why this is happening, and how to get this VM to respect the semantics of the shutdown command again? -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature