From owner-freebsd-current@FreeBSD.ORG  Mon May 12 07:40:59 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A1B7A37B401; Mon, 12 May 2003 07:40:59 -0700 (PDT)
Received: from gold.he.net (gold.he.net [216.218.149.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BAEC343FE5; Mon, 12 May 2003 07:40:56 -0700 (PDT)
	(envelope-from daver@gomerbud.com)
Received: from tombstone.localnet.gomerbud.com
	(adsl-63-196-194-182.dsl.snlo01.pacbell.net [63.196.194.182]) by gold.he.net
	(8.8.6p2003-03-31/8.8.2) with ESMTP id HAA09894; Mon, 12 May 2003 07:40:53
	-0700
Received: by tombstone.localnet.gomerbud.com (Postfix, from userid 1001)
	id 7709C409; Mon, 12 May 2003 07:40:44 -0700 (PDT)
Date: Mon, 12 May 2003 07:40:44 -0700
From: "David P. Reese Jr." <daver@gomerbud.com>
To: Robert Watson <rwatson@freebsd.org>
Message-ID: <20030512144044.GA7265@tombstone.localnet.gomerbud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
cc: current@freebsd.org
Subject: Re: rpc.lockd spinning; much breakage
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2003 14:41:00 -0000

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)