Thomas Feddersen wrote:
> When I boot my system, rpcbind and mountd come up okay, but the actual 
> nfs deamon and lockd and statd don't.
>
> In /var/log/messages I found immediately after the boot messages:
> Feb 10 18:39:59 Ximus nfsd[211]: nfssvc: Operation not permitted
> Feb 10 18:39:59 Ximus nfsd[212]: nfssvc: Operation not permitted
> Feb 10 18:39:59 Ximus nfsd[213]: nfssvc: Operation not permitted
> Feb 10 18:39:59 Ximus nfsd[214]: nfssvc: Operation not permitted
> Feb 10 18:39:59 Ximus nfsd[210]: can't register with udp portmap
> but I have no idea what that wants to tell me.
>
> I looked around a little in /usr/etc/rc.d and I have the idea that the 
> names of the scripts have been changed. It appears to me that contrary 
> to the NetBSD-guide at
> http://www.netbsd.org/guide/en/chap-net-misc.html#chap-net-misc-nfs
> the following changes have occurred:
> 1- "nfs_server" and "nfs_client" have been combined into "nfsd"
> 2- "lockd" and "statd" have been renamed "rpc.lockd" and "rpc.statd" 
> respectively
> 3- and combined into "nfslocking"
>
> The scripts "nfsd" and "nfslocking" don't start the daemons but also 
> don't produce an errormessage nor any message at all.
>
> As a workaround I can start "nfsd"; "rpc.lockd" and "rpc.statd" from 
> the commandline, "rpc.lockd" and "rpc.statd" register in /var/run but 
> "nfsd" doesn't. Although nfs works afterwards, I have an eerie feeling 
> that something may be wrong.
>
> I have tried different systems: NetBSD 4.0_BETA2 (i386 or Xen) and 
> NetBSD 3.0 (i386) show the same behaviour.
>
> I would like to be able to start nfs automatically via the rc.d system 
> at boot up - does anybody have an idea?
>
> Kind Regards
> Thomas Feddersen
> Hamburg GER
> engineering for pleasure and profit
>
Here's what I have on my NFS server:

rpcbind=yes
mountd=yes
nfs_server=yes
lockd=yes
statd=yes