Date: Tue, 7 Mar 2006 12:50:00 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Miguel Ramos <miguel@anjos.strangled.net> Cc: Jun Kuriyama <kuriyama@imgsrc.co.jp>, freebsd-stable@freebsd.org Subject: Re: rpc.lockd brokenness (2) Message-ID: <20060307175000.GA96569@xor.obsecurity.org> In-Reply-To: <1141753136.2976.14.camel@dual.anjos.strangled.net> References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> <1141685806.3294.4.camel@dual.anjos.strangled.net> <7mu0abuq2u.wl%kuriyama@imgsrc.co.jp> <1141753136.2976.14.camel@dual.anjos.strangled.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 07, 2006 at 05:38:56PM +0000, Miguel Ramos wrote: >=20 > The problem I'm having is not exactly what is described in pr bin/80389, > although it is very much related. So, I'm unable to verify if the patch > you gave corrects the problem, since the problem is not visible on my > systems. >=20 > I do have a lockd hang, however... Here is as much data as I can gather: >=20 > 1- Only one client machine of all I have, the only one which is remote > booted, hangs on startup with rpc.lockd/rpc.statd enabled. Just to verify: lockd is enabled on BOTH client AND server? Kris --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEDcfIWry0BWjoQKURAv/FAKCF5yyNFXa5oXJK7ZLHH57N97DqtwCgt9wr 6TzH6G7nlt6q2daqJzPn5k4= =b1MD -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060307175000.GA96569>