Comment # 2 on bug 1183123 from Michael Hirmke

(In reply to Jonathan Kang from comment #1)
> (In reply to Michael Hirmke from comment #0)
> > Using the combination nfs, systemd, NetworkManager and nscd I always run
> > into the problem, that NetworkManager states the system being online, before
> > it is really online. In this case, all nfs mounts by systemd are failing,
> > because the names of the servers can't be resolved at that time.
> > Later NM's nfs dispatcher script works, but also comes too late for some
> > services, that are started by systemd in the meantime.
> > Using Networkmanager-wait-online for these services doesn't help either,
> > because - as stated above - NM believes it is online long before it really
> > is.
> > 
> > Disabling nscd in this case cures the problem. After doing so, even systemd
> > is able to mount the nfs shares. Everything is placed in the correct order.
> 
> NetworkManager has dropped nscd support quite a long while ago. So I guess
> it's
> nscd that interferes DNS resolution.
> > 
> > Is this a bug? Or is it ok for this scenario to disable nscd? Or do I have
> > to use special settings for this case?
> 
> What do you use nscd for? You can disable nscd if you don't need it.

I don't use it for anything and indeed deactivated it, but the default for
Tumbleweed is an activated nscd. So I just wondered what might be wrong in my
system.