From owner-freebsd-questions@FreeBSD.ORG Fri Aug 26 19:06:06 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 471E916A41F for ; Fri, 26 Aug 2005 19:06:06 +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 DF4B643D46 for ; Fri, 26 Aug 2005 19:06:05 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 0546A5CC2; Fri, 26 Aug 2005 15:06:05 -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 79299-09; Fri, 26 Aug 2005 15:06:02 -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 8A43E5C53; Fri, 26 Aug 2005 15:06:02 -0400 (EDT) Message-ID: <430F6828.2070109@mac.com> Date: Fri, 26 Aug 2005 15:06:16 -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 Beach House References: <200508261803.j7QI3J0W071198@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200508261803.j7QI3J0W071198@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:06:06 -0000 Tuc at Beach House wrote: > We are having a problem on a 5.4 NFS server where at times > mountd seems to be just "disappearing". Is there a good way to track > that this happens, or to find out what causes it to die? 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. The first step is to look for log messages (see mountd's "-d" flag), and to unlimit coredumpsize (see /etc/login.conf and the shell environment) and see whether you can get a coredump for gdb. It'll help to rebuild mountd with -g for debugging purposes... -- -Chuck