Date: Wed, 13 Nov 2002 18:38:27 -0800 From: Kris Kennaway <kris@FreeBSD.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Kris Kennaway <kris@FreeBSD.org>, current@FreeBSD.org, alfred@FreeBSD.org Subject: Re: rpc.lockd problems Message-ID: <20021113183827.C5919@citusc.usc.edu> In-Reply-To: <3DD306C1.41DFA8D4@mindspring.com>; from tlambert2@mindspring.com on Wed, Nov 13, 2002 at 06:13:21PM -0800 References: <20021113164143.C4476@citusc.usc.edu> <3DD306C1.41DFA8D4@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 13, 2002 at 06:13:21PM -0800, Terry Lambert wrote: > Kris Kennaway wrote: > > A few months ago I posted about rpc.lockd interop problems I am having > > between my 5.0 NFS client and a Redhat 7.1 server. Both are running > > rpc.lockd, but when I send a lock request to the server it hangs > > forever blocked on the /var/run/lock socket. > > > > tcpdump shows that the lock RPC request is being sent, and answered by > > the server. I have the complete tcpdump trace if anyone is > > interested. > > This might be a long standing problem that FreeBSD has serving > UDP NFS client requests. > > You need to look at the packets. Is the IP on the response the > same as the one on the request? Yes, and I have no problems interoperating NFS under 4.x between these machines (or under 5.0 as long as I don't try and lock any files) - it's just 5.0's rpc.lockd. Kris 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?20021113183827.C5919>