kern/50807: NFS file locking as client deos not working
Bruce Evans
bde at zeta.org.au
Sat Apr 12 22:45:23 PDT 2003
On Sat, 12 Apr 2003, Doug Barton wrote:
> > At least for a -current server and client, one or both rpc.lockd and
> > rpc.statd enabled here on one or both of the client and server. IIRC,
> > enabling both on both works but may be more than necessary. rc.conf.5
> > is very unclear on the exact servers required.
>
> rpc.statd(8) is much more clear. :)
I think it is only clear if you don't need to read it to know what it does.
> Both are required. In -current, using
> rcNG, you should always get rpc.statd if you ask for rpc.lockd. If that's
> not happening, we need to fix the scripts, but I'm pretty sure it is
> actually happening. I'll try to remember to double-check this.
I use -uncurrent and rc_ng="NO" :-).
rc_ng doesn't seem to be any different from rc_og here. There are
separate knobs for rpc.lockd and rpc.statd, and both rc.network and
rc.d/nfslocking honor the (apparently independent) configured settings
for both. Neither rc_ng nor rc_og is fully bug-for-bug compatible
with rc.conf.5 which says that these variables are only used for nfs
servers. The man page was correct before rev.1.143 of rc.network.
Bruce
More information about the freebsd-bugs
mailing list