DAEMONS=(syslog-ng !hotplug !pcmcia network portmap netfs crond sshd proftpd samba nfslock !nfsd distccd)
]]>Interesting... it takes forever to load when it is called from rc.conf, but is zippy quick when called from userspace using /etc/rc.d/nfsd start
I'm sorry to say that I don't know the first thing about NFS, but I have one or two thoughts about the slow loading you mentioned.
It's possible (although I doubt it) that this is because /etc/profile isn't sourced when the nfsd initscript is called from rc.multi.
It's also possible (and somewhat more likely i think) that nfsd is started with too short a delay after /etc/rc.d/network. Try putting nfsd last in the DAEMONS array in rc.conf
]]>[jvinet@pluto ~]$ zcat /proc/config.gz | grep NFS
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
# CONFIG_NCPFS_NFS_NS is not set
I know somebody here has to be using NFS!
]]>/etc/conf.d/nfsd on the server
NFSD_OPTS=8
MOUNTD_OPTS="--nfs-version 3"
Command on the client that doesn't work
# mount -t nfs 192.168.1.5:/mnt/lv0/recordings /mnt/myth/recordings/ -o nfsvers=3,hard,intr
NFSv3 not supported!
mount: wrong fs type, bad option, bad superblock on 192.168.1.5:/mnt/lv0/recordings,
or too many mounted file systems
Command on the client that does work
# mount -t nfs 192.168.1.5:/mnt/lv0/recordings /mnt/myth/recordings/ -o nfsvers=2,hard,intr
Soooo... even though the server is set to nfs3, the client can't seem to connect that way. :?
]]>