Date: Tue, 7 Mar 2006 13:08:20 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Miguel Lopes Santos Ramos <miguel@anjos.strangled.net> Cc: kuriyama@imgsrc.co.jp, freebsd-stable@freebsd.org, kris@obsecurity.org Subject: Re: rpc.lockd brokenness (2) Message-ID: <20060307180820.GA35621@xor.obsecurity.org> In-Reply-To: <200603071756.k27HuMrQ001718@compaq.anjos.strangled.net> References: <20060307175000.GA96569@xor.obsecurity.org> <200603071756.k27HuMrQ001718@compaq.anjos.strangled.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 07, 2006 at 05:56:22PM +0000, Miguel Lopes Santos Ramos wrote: > > > 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 >=20 > Oh yes. If any of the daemons is not enabled on both machines there's no > locking, there's no system hang and all that occurs is: > can't open or create /var/run/cron.pid: Operation not supported. OK, thanks. Please try to obtain a tcpdump -vvv trace of the broken operation. Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEDcwUWry0BWjoQKURAoSKAKDNfcvDDRmBH5wbLA044wB+XOXOqgCg9o7t XYa/2RkU2iJdQtly6lr30+0= =+ki2 -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060307180820.GA35621>