systemd depends so heavily on a files it can not reboot

[John Reiser]

On 07/08/2013, Adam Pribyl wrote:
> On Mon, 8 Jul 2013, "Jóhann B. Guðmundsson" wrote:
> 
>> No need to open a discussion. SysRq is disable for are a reason and what you are propose allows anyone that sits at the keyboard to kill all process,reboot without syncing or authorization and all because you got a corrupted filesystem.
> 
> OK, so the systemd people say, it is perfecly fine you can not reboot via ctrl-alt-del (while it was always possible with init) and give me the advice to enable sysrq for the purpose, and sysrq people say, it's not for users, we will not enable it, it is dangerous.
> 
> Now I have a server, what should I do there?

1. Install a userid whose login shell is /usr/bin/sync
   (or a script which does "sync; sync")
2. Login as the sync user (twice, perhaps.)
3. Press the hardware reset switch (or call your co-location
   provider and have them press it for you; or otherwise force
   a reboot via hardware means.)