Date: Thu, 14 Nov 2002 12:07:50 -0800 From: Kris Kennaway <kris@obsecurity.org> To: "Andrew P. Lentvorski" <bsder@mail.allcaps.org> Cc: Kris Kennaway <kris@FreeBSD.org>, Terry Lambert <tlambert2@mindspring.com>, alfred@FreeBSD.org, current@FreeBSD.org Subject: Re: rpc.lockd problems Message-ID: <20021114200749.GB11056@rot13.obsecurity.org> In-Reply-To: <20021114004418.O675-100000@mail.allcaps.org> References: <20021113183827.C5919@citusc.usc.edu> <20021114004418.O675-100000@mail.allcaps.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--7ZAtKRhVyVSsbBD2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 14, 2002 at 01:47:43AM -0800, Andrew P. Lentvorski wrote: > On Wed, 13 Nov 2002, Kris Kennaway wrote: >=20 > > 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. >=20 > Can you help isolate the problem by trying this same operation from a > Solaris NFS client? I'm actually happy to get bug reports about rpc.lockd > as it means that someone is actually using my code. However, after having > rewritten and debugged the FreeBSD rpc.lockd, I have no desire to debug > the Linux one. ;) Sorry, I have no access to a Solaris machine :( Kris --7ZAtKRhVyVSsbBD2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE91AKVWry0BWjoQKURAsGuAKDD6ykLLQFMM7SsNkyij7fl8jdn1ACfXeqm zfWTRl5yLN6TPJBusSWmaYk= =Fz2p -----END PGP SIGNATURE----- --7ZAtKRhVyVSsbBD2-- 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?20021114200749.GB11056>