Date: Sat, 12 Apr 2003 22:00:28 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/50807: NFS file locking as client deos not working Message-ID: <200304130500.h3D50S1f029875@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR kern/50807; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: Doug Barton <DougB@freebsd.org> Cc: Shao Zhang <shao@cia.com.au>, "" <FreeBSD-gnats-submit@freebsd.org> Subject: Re: kern/50807: NFS file locking as client deos not working Date: Sun, 13 Apr 2003 14:56:46 +1000 (EST) [Another copy for gnats.] 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. Brucehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304130500.h3D50S1f029875>