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. -a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
