Bug#791391: NFS mounts and other things fail if DHCP hasn't finished

[Michael Biebl]

Am 04.07.2015 um 14:22 schrieb Daniel Pocock:
> 
> 
> On 04/07/15 13:58, Michael Biebl wrote:
>> Am 04.07.2015 um 11:38 schrieb Daniel Pocock:
>>> Package: systemd Version: 215-17+deb8u1 Severity: important
>>>
>>> This has been happening on a system that was upgraded from wheezy
>>> to jessie
>>>
>>> Sometimes systemd starts the network and then tries to start
>>> things that depend on the network (e.g. ntpdate, NFS client

Isn't ntpdate (*) started via an if-up.d hook i.e. not by systemd itself?


>>> mounts) before DHCP has obtained a lease.
>>>
>>> Sometimes the boot completely stops and asks for root login
>>>
>>> Sometimes it reaches the X login but if a user logs in, it throws
>>> them out because their home is not mounted.
> 
>> Is home mounted via NFS?
> 
> 
> /home is a local filesystem

Is /home mountend reliably by systemd?

> /home/username is on NFS

How is /home/username mounted? Via /etc/fstab, autofs, something else?

Just trying to find out what exactly fails and what not.


(*) As a side note: you might want to consider enabling
systemd-timesyncd.service (and removing ntpdate). timesyncd is a very
lightweight NTP client.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150704/4e32a741/attachment-0002.sig>