Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #239682
| From | "sp007@caiway.net" <sp007@caiway.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: /usr/sbin/reboot: disabled in systemd-nspawn container |
| Date | 2021-09-04 17:40 +0200 |
| Message-ID | <CTFVU-4RR-7@gated-at.bofh.it> (permalink) |
| References | <CTDr3-3br-1@gated-at.bofh.it> <CTEwN-45T-1@gated-at.bofh.it> |
| Organization | amd |
On Sat, 4 Sep 2021 16:42:45 +0300
Reco <recoverym4n@enotuniq.net> wrote:
> Hi.
> /bin/systemd reboot
>
> And, what about these:
>
> ls -al /sbin/reboot
> file /sbin/reboot
>
> Reco
>
the commands poweroff and reboot are textfiles.
I have no idea
# mcedit /sbin/reboot:
#!/bin/sh
echo "${0}: disabled in systemd-nspawn container"
if [ -e /etc/open-infrastructure/container/shutdown.txt ]
then
cat /etc/open-infrastructure/container/shutdown.txt
elif [ -e /usr/share/open-infrastructure/container/shutdown.txt ]
then
cat /usr/share/open-infrastructure/container/shutdown.txt
fi
exit 1
#eof
# mcedit /sbin/poweroff:
#!/bin/sh
echo "${0}: disabled in systemd-nspawn container"
if [ -e /etc/open-infrastructure/container/shutdown.txt ]
then
cat /etc/open-infrastructure/container/shutdown.txt
elif [ -e /usr/share/open-infrastructure/container/shutdown.txt ]
then
cat /usr/share/open-infrastructure/container/shutdown.txt
fi
exit 1
# cat /usr/share/open-infrastructure/container/shutdown.txt
Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.
However, please contact your system administrator to reboot this
container from the host system.
So the reason is found, now I have to find out who/what take over these
basic commands
I have no packages with open-infrastructure installed
tia
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
/usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 15:00 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Reco <recoverym4n@enotuniq.net> - 2021-09-04 16:10 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 17:10 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Reco <recoverym4n@enotuniq.net> - 2021-09-04 17:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Greg Wooledge <greg@wooledge.org> - 2021-09-04 18:00 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Stefan Monnier <monnier@iro.umontreal.ca> - 2021-09-04 19:20 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container Greg Wooledge <greg@wooledge.org> - 2021-09-04 19:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container The Wanderer <wanderer@fastmail.fm> - 2021-09-04 21:10 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 22:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 17:40 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED "sp007@caiway.net" <sp007@caiway.net> - 2021-09-04 18:00 +0200
Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED Andrei POPESCU <andreimpopescu@gmail.com> - 2021-09-12 09:50 +0200
csiph-web