Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Apr 2003 21:40:09 -0700 (PDT)
From:      Shao Zhang <shaoz@activesky.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/50807: NFS file locking as client deos not working
Message-ID:  <200304140440.h3E4e9Ah082098@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

The following reply was made to PR kern/50807; it has been noted by GNATS.

From: Shao Zhang <shaoz@activesky.com>
To: Doug Barton <DougB@FreeBSD.org>
Cc: Bruce Evans <bde@zeta.org.au>, freebsd-bugs@FreeBSD.org,
	FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/50807: NFS file locking as client deos not working
Date: Mon, 14 Apr 2003 14:35:06 +1000

 On [Sun, 13 Apr 2003 21:22:51 -0700 (PDT)], Doug Barton <DougB@FreeBSD.org> wrote:
 > On Mon, 14 Apr 2003, Shao Zhang wrote:
 >
 >> My understanding is that you only need to enable lockd and statd for the
 >> server. According to man rc.conf:
 >
 > Unfortunately, the rc docs haven't been updated properly in this regard.
 > The nature of RPC services pretty much requires rpc.statd. If you're using
 > locking, you definitely need it on both the client and server.
 
 I have tried to enable both rpc.lockd and rpc.statd on FreeBSD. The
 Linux file server runs rpc.lockd in kernel mode and rpc.statd is running
 as well. Now any program that requires file locking simply hangs on FreeBSD.
 
 I verified this using bogofilter -s < ~/Mail/spam, or just mutt -f
 ~/Mail/spam.
 
 If you do a strace on it, it hangs on fcntl(..., O_FSETLK, ...)
 
 Currently, I am using nolockd in /etc/fstab as a workaround.
 
 Regards,
 
 Shao.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304140440.h3E4e9Ah082098>