On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote: > On Sat, 4 Sep 2021 16:42:45 +0300 > Reco <recovery...@enotuniq.net> wrote: > > > Hi. > > > > On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote: > > > Suddenly I can no longer reboot or poweroff my up-to-date > > > bullseye system: > > > > > > # reboot > > > /usr/sbin/reboot: disabled in systemd-nspawn container > > > > Unless I'm mistaken, these messages are not generated by systemd. > > In fact, there's nothing that resembles such messages in systemd > > sources. > > > > So, try this, for starters: > > > > /bin/systemd reboot > > > > # /bin/systemd reboot > Excess arguments. > > > And, what about these: > > > > ls -al /sbin/reboot > > # ls -al /sbin/reboot > -rwxr-xr-x 1 root root 319 Mar 24 05:22 /sbin/reboot > > > > file /sbin/reboot > > > > # file /sbin/reboot > /sbin/reboot: POSIX shell script, ASCII text executable
That's not normal for a bullseye system using systemd for init. unicorn:~$ ls -l /sbin/reboot lrwxrwxrwx 1 root root 14 Jul 13 13:29 /sbin/reboot -> /bin/systemctl* You might need to reinstall the systemd-sysv package, maybe. I'm not sure what you did or how your system got into this state.
