From owner-freebsd-questions@FreeBSD.ORG Fri Aug 26 19:48:35 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD84C16A452 for ; Fri, 26 Aug 2005 19:48:35 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B57643D46 for ; Fri, 26 Aug 2005 19:48:35 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id C88515CF8; Fri, 26 Aug 2005 15:48:34 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79613-02; Fri, 26 Aug 2005 15:48:32 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 2CE395C34; Fri, 26 Aug 2005 15:48:32 -0400 (EDT) Message-ID: <430F721E.5080704@mac.com> Date: Fri, 26 Aug 2005 15:48:46 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tuc at T-B-O-H References: <200508261930.j7QJUQx0073021@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200508261930.j7QJUQx0073021@himinbjorg.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-questions@freebsd.org Subject: Re: Why would mountd die? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Aug 2005 19:48:35 -0000 Tuc at T-B-O-H wrote: [ ... ] >>DJB's daemontools come to mind, also Big Brother (www.bb4.org) can monitor a >>system, keeping track of the running processes, and yell (ie, email you, page >>you, etc) if something bad happens. >> > > Ok, thanks. > >>The first step is to look for log messages (see mountd's "-d" flag), >> > > :-/ Logs to sysout, so can't be run from the /etc/rc.d/mountd. Was > hoping to have it log to syslog. I guess I could wrap a shell around it. Or use -d with daemontools, that's pretty much the intended purpose. The thing is, watch out for binding with portmap or whatever it's called nowadays (rpc.portmapd? rpcbind?), you can feed mountd the -p flag, but you might have to adjust the clients then, too. >> and to unlimit coredumpsize (see /etc/login.conf and the shell >> environment) and see whether you can get a coredump for gdb. > > If its run as root, isn't coredumpsize already unlimited? Maybe. Kinda depends on what the default is and whether it's been changed somewhere down the line. It's something to check. :-) >>It'll help to rebuild mountd with -g for debugging purposes... >> > > If I can get it to do the core, might be the best idea. > > I decided to run it in a screen to see if I can see maybe something > that way. If it gives a clue, maybe won't have to increase coredumpsize > and compile with debug for gdb. OK. -- -Chuck