Mailinglist Archive: opensuse-bugs (3392 mails)
| < Previous | Next > |
[Bug 744293] systemd: vdr starts before nfs-client-mount ?!
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 1 Feb 2012 11:27:48 +0000
- Message-id: <20120201112748.BE65C245523@molor.provo.novell.com>
https://bugzilla.novell.com/show_bug.cgi?id=744293
https://bugzilla.novell.com/show_bug.cgi?id=744293#c3
--- Comment #3 from Marius Tomaschewski <mt@xxxxxxxx> 2012-02-01 11:27:46 UTC
---
Do you have an DHCPv6 server in your network or only DHCPv4?
When you don't have DHCPv6 server, change to use BOOTPROTO=dhcp4
in /etc/sysconfig/network/ifcfg-eth0 -- this will speed up the
network start / cause to not wait for DHCPv6.
vdr deps are: # Required-Start: $remote_fs
nfs deps are: # Required-Start: $network $portmap
that means (/etc/insserv.conf):
$network network
$remote_fs $local_fs +nfs +cifs
vdr waits for the mandatory $local_fs and when enabled also for
nfs and cifs. nfs waits for network (that waits for $local_fs).
So the dependencies are IMO correct.
It looks like systemd would start vdr after network, but
would not wait until it finished...?
I've an "evil" suspicion, that I'll verify...
The error message is:
Jan 31 17:45:45 t3 vdr: [1141] ERROR: /var/spool/video: No such file or
directory
this means that the mount-point is not there, so nfs script can't even
mount the nfs export.
Please fix it using:
mkdir /var/spool/video
--
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.
| < Previous | Next > |