Date: Fri, 22 Sep 2006 21:25:21 +0200 From: Robert Joosten <robert@ml.erje.net> To: Chuck Swiger <cswiger@mac.com> Cc: questions@freebsd.org Subject: Re: 6.1 and NFS Message-ID: <20060922192520.GD918@iphouse.com> In-Reply-To: <186AD616-6739-41EF-88F1-4F8B9BD417BC@mac.com> References: <C87B42D9-AF83-4DFC-9E13-53FCD874A444@obmail.net> <20060921182252.GA24321@xor.obsecurity.org> <20060921214316.GD673@iphouse.com> <6180D198-A44B-46D0-8A0B-FC5D3ACA115C@mac.com> <20060922180202.GB918@iphouse.com> <186AD616-6739-41EF-88F1-4F8B9BD417BC@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > >I observed running a pxe client running fbsd 5.[45] being served by > >nfs-box running 5 (and 4 > >nowadays because of asr0 trouble due to geom) having disabled > >rpc.lockd > >the box doens't let me run adduser, but with rpc.lockd enabled it's > >fine > >with 'em. Is that strange or am I missing (some) insight about this > >matter? > That's interesting. Are you getting a "could not lock the passwd > file: EOPNOTSUPP" failure with rpc.lockd not enabled? I never witnissed any message. After I press enter (adduser) nothing appears on the screen at all. But it has been a long time ago and I'm currently unable to experiment. I hope tomorrow I will. I assume it's a good idea to run a debug kernel ? I also recall there were some occaisions I once run adduser that went ok, but the second (and more) times in a row it just locked. These cases were never reproducable, however I had the idea something called some rpc.lockd procedure before. In all these cases, the box ran the standard sendmail enabled. Maybe in these occasions the box did a 'lock' before, and all subsequent flock() calls stall. Something like that. I'm not sure but at that time I presume I ran a 6.0-rel pxe client served by a 5.3-rel nfs server; I really forget though and didn't take any notes either. Regards, Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060922192520.GD918>