[gentoo-user] systemd: incorrect behavior when doing poweroff/reboot

[gentoo-user] systemd: incorrect behavior when doing poweroff/reboot

[walt]

I'd be 100% sure this is a systemd bug except that the problem is so
obvious and (I think) so common that I can't believe I'm the only
systemd user seeing it:

I routinely share /usr/portage over NFS between several gentoo boxes
on my wireless network.  When I poweroff or reboot the NFS client
machines, systemd tears down the wireless connection *before* it
unmounts the /usr/portage share, and so the umount command hangs and
the machine won't shut down.

I'd think people that hang out in this list must do the same thing,
surely?  No one else here running into this silly problem?

[gentoo-user] Re: systemd: incorrect behavior when doing poweroff/reboot

[Hans]

On 22/03/15 08:44, walt wrote:
> I'd be 100% sure this is a systemd bug except that the problem is so
> obvious and (I think) so common that I can't believe I'm the only
> systemd user seeing it:
>
> I routinely share /usr/portage over NFS between several gentoo boxes
> on my wireless network.  When I poweroff or reboot the NFS client
> machines, systemd tears down the wireless connection *before* it
> unmounts the /usr/portage share, and so the umount command hangs and
> the machine won't shut down.
>
> I'd think people that hang out in this list must do the same thing,
> surely?  No one else here running into this silly problem?
>
>
>
Had the same and various other problem. Resolved it by giving systemd 
the boot. No more problems with after I changed to openrc.

Re: [gentoo-user] Re: systemd: incorrect behavior when doing poweroff/reboot

[Alan McKinnon]

On 22/03/2015 03:32, Hans wrote:
> On 22/03/15 08:44, walt wrote:
>> I'd be 100% sure this is a systemd bug except that the problem is so
>> obvious and (I think) so common that I can't believe I'm the only
>> systemd user seeing it:
>>
>> I routinely share /usr/portage over NFS between several gentoo boxes
>> on my wireless network.  When I poweroff or reboot the NFS client
>> machines, systemd tears down the wireless connection *before* it
>> unmounts the /usr/portage share, and so the umount command hangs and
>> the machine won't shut down.
>>
>> I'd think people that hang out in this list must do the same thing,
>> surely?  No one else here running into this silly problem?
>>
>>
>>
> Had the same and various other problem. Resolved it by giving systemd
> the boot. No more problems with after I changed to openrc.
> 

Surely that's a simple matter of adjusting the shutdown order in the
unit files for those packages?

Open a bug and the package maintainer will correct it.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] systemd: incorrect behavior when doing poweroff/reboot

[Rich Freeman]

On Sat, Mar 21, 2015 at 6:44 PM, walt <w41ter@gmail.com> wrote:
> I'd be 100% sure this is a systemd bug except that the problem is so
> obvious and (I think) so common that I can't believe I'm the only
> systemd user seeing it:
>
> I routinely share /usr/portage over NFS between several gentoo boxes
> on my wireless network.  When I poweroff or reboot the NFS client
> machines, systemd tears down the wireless connection *before* it
> unmounts the /usr/portage share, and so the umount command hangs and
> the machine won't shut down.
>
> I'd think people that hang out in this list must do the same thing,
> surely?  No one else here running into this silly problem?
>

Log a bug.  systemd is very new, and if you have a somewhat-unusual
configuration (nfs over wifi, for example) it is entirely possible
that nobody has noticed a bug like this.  I was having issues with an
nfs root with dracut+systemd and I found the maintainers of both very
interested in bug reports and testing.

It seems likely that a dependency is unspecified somewhere.

As far as whether the bug is in systemd or dracut, if you have systemd
enabled on dracut then dracut will be running systemd anyway, so the
config issue will get you either way.

-- 
Rich