https://bugzilla.novell.com/show_bug.cgi?id=774502 https://bugzilla.novell.com/show_bug.cgi?id=774502#c24 --- Comment #24 from Marius Tomaschewski <mt@suse.com> 2013-01-17 16:57:25 UTC --- (In reply to comment #23)
/etc/init.d/nfs ...relates to the classical startup sequence, no?
Yes.
Sorry, I'm not an expert in systemd or init scripts, I just can see from the LSB-header if /etc/init.d/nfs that it requires the network to be started.
Network yes, but neither $time (ntp) nor $named. And it will never work with STARTMODE='ifplugd' or NetworkManager, unless you handle it yourself via ifservices(5) or NetworkManager dispatcher scripts. => Use STARTMODE=auto or STARTMODE=nfsroot. AFAIS it fails because name resolution (comment 7). Does your /etc/resolv.conf contains the correct name server settings when the network is completely up? Are you able to resolve the hostnames used in fstab then (e.g. "host nfsserver")?
And that was nicely working in old times. With systemd obviously not. So IMHO this is a problem in systemd, or am I wrong?
systemd makes much more in parallel. You can try to double the WAIT_FOR_INTERFACES and DHCLIENT_WAIT_AT_BOOT that are in /etc/sysconfig/network/{config,dhcp}. When these timeouts expire for some reason, /etc/init.d/network reports 0 (success) to the systemd even the network is not completely started. Please attach a supportconfig (install supportutils) output. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.