I forgot to say the system is halting normally with the audit=0 thing.
On Tue, Apr 16, 2013 at 9:22 AM, Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Tue, Apr 16, 2013 at 09:54:29AM +0100, Colin Guthrie wrote: > > 'Twas brillig, and Zbigniew Jędrzejewski-Szmek at 15/04/13 19:48 did > > gyre and gimble: > > > On Mon, Apr 15, 2013 at 08:36:33PM +0200, Zbigniew Jędrzejewski-Szmek > wrote: > > >> On Mon, Apr 15, 2013 at 02:31:56PM -0300, Chir0n wrote: > > >>> # yum -y --releasever=19 --nogpg --installroot=/srv/mycontainer > > >>> --disablerepo='*' --enablerepo=fedora install systemd passwd yum > > >>> fedora-release vim-minimal > > >>> # systemd-nspawn -bD > > >>> /srv/mycontainer > > >> > > >> sudo nsenter -t $PID -m -u -i -n -p /bin/bash > > > Hm, if I say 'halt' in this bash window, I see > > > > > > bash-4.2# halt > > > bash-4.2# [1] + 14306 suspended (signal) sudo nsenter -t 13221 -m -u > -i -n -p /bin/bash > > > > > > and the container's init hangs after 'All filesystems unmounted.'. > > > > > > Only when I do 'fg', halt resume and systemd-nspawn quits. > > > > > > Apparrently only happens rarely (1/5 so far). > > > > > > What's going on? > > > > Isn't "halt" meant to, well, halt? Perhaps it behaves differently under > > nspawn but I thought that was the primary difference between "halt" and > > "poweroff" > Eeeeee, yeah, the system is supposed to halt and it's not doing that :) > > Zbyszek > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel