Date: Tue, 7 Mar 2006 18:58:45 GMT From: Miguel Lopes Santos Ramos <miguel@anjos.strangled.net> To: kris@obsecurity.org Cc: kuriyama@imgsrc.co.jp, freebsd-stable@freebsd.org Subject: Re: rpc.lockd brokenness (2) Message-ID: <200603071858.k27IwjDP002136@compaq.anjos.strangled.net> In-Reply-To: <20060307180820.GA35621@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> OK, thanks. Please try to obtain a tcpdump -vvv trace of the broken > operation. > > Kris I have it. I had just to disable cron startup, which was the only daemon that used pidfile_open and started after statd/lockd, and then start it by hand. Now, perhaps it is better to post it off-list, since it is 69kB for -vvv or 196kB for -X -vvv. Are you willing to look at the dump yourself? Anyone? BTW, cron was left in an unkillable state, it couldn't be killed with SIGKILL. In the meanwhile, I'll try to revert lib/libutil/pidfile.c to Jan 1st, which is my suspect. Miguel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603071858.k27IwjDP002136>