You are not logged in.
I have a feeling this should have been already asked, but my Googlefu is not giving me anything.
My NFS mounts fail to mount at boot; I suspect because I haven't obtained my DHCP lease before 'netfs' daemon is run. Is there a way I can make netcfg wait for the lease before returning for boot to continue with the rest of the daemons (including netfs)?
My DAEMONS:
DAEMONS=( @syslog-ng net-profiles iptables rpcbind netfs @crond @sshd dbus @mpd @xinetd @sensors @smartd @mdadm ptal-init @cupsd @ntpd)The NFS shares mount fine after boot by issuing `mount -a`
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
nfs-common?
Offline
Ooops.
Why do they mount fine after boot though? I don't manually start nfs-common.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
It doesn't need to use daemons for manual mount nfs directories. I think kernel's module kernel/fs/nfs/nfs.ko.gz perfoms the client function.
About year ago you could write only one daemon nfs-common. Rpcbind is started as dependence.
Last edited by solamir (2012-09-04 10:21:05)
Offline
I used to get around this by putting netfs in POST_UP in my profile - worked fine, apart from initscripts nagging me about using one daemon to start another. ![]()
Alternatively, switch to systemd. which handles this automatically.
Offline
About year ago you could write only one daemon nfs-common. Rpcbind is started as dependence.
I'll try swapping rpcbind for nfs-common and see how that goes.
Alternatively, switch to systemd.
lol.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline