Date: Mon, 12 May 2003 07:40:44 -0700 From: "David P. Reese Jr." <daver@gomerbud.com> To: Robert Watson <rwatson@freebsd.org> Cc: current@freebsd.org Subject: Re: rpc.lockd spinning; much breakage Message-ID: <20030512144044.GA7265@tombstone.localnet.gomerbud.com>
next in thread | raw e-mail | index | archive | help
On Mon, 12 May 2003 10:19:00 -0400 (EDT) Robert Watson wrote:
> Is there a way to get rpc.lockd on the server to dump it's state to a
> file?
Just send it any of the signals which default to creating a core image.
Check out signal(3). Sending it SIGQUIT with kill should work as long as
rpc.lockd doesn't catch SIGQUIT. It would also be helpful if you rebuilt
the binary with debugging symbols.
--
David P. Reese Jr. daver@gomerbud.com
--------------------------------------------------------------------------
It can be argued that returning a NULL pointer when asked to allocate
zero bytes is a silly response to a silly question.
-- FreeBSD manual page for malloc(3)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030512144044.GA7265>