Date: Tue, 18 Mar 2003 19:03:47 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "Andrew P. Lentvorski, Jr." <bsder@allcaps.org> Cc: Steve Sizemore <steve@ls.berkeley.edu>, current@freebsd.org Subject: Re: NFS file unlocking problem Message-ID: <3E77DE13.11BA7743@mindspring.com> References: <Pine.LNX.4.44.0303181722440.21978-100000@mail.allcaps.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Andrew P. Lentvorski, Jr." wrote: > On Tue, 18 Mar 2003, Steve Sizemore wrote: > > > root 399 0.0 0.1 263496 1000 ?? Is 9:11AM 0:00.00 /usr/sbin/rpc.sta > > root 402 0.0 0.1 1512 1156 ?? Ss 9:11AM 0:00.00 /usr/sbin/rpc.loc > > daemon 405 0.0 0.1 1484 1176 ?? I 9:11AM 0:00.00 /usr/sbin/rpc.loc > > This might be the culprit. The way that rpc.lock works is that it grabs a > lock on the *entire* underlying file when any lock request comes in. If > those requests get misrouted to the wrong daemon, it is likely to cause > havoc. I thought this was a fork on purpose, and the second one was there for LOCK vs. LOCKW requests? If not, how the heck is he starting this in the first place?!? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E77DE13.11BA7743>