Date: Fri, 26 Aug 2005 15:06:16 -0400 From: Chuck Swiger <cswiger@mac.com> To: Tuc at Beach House <tuc@tucs-beachin-obx-house.com> Cc: freebsd-questions@freebsd.org Subject: Re: Why would mountd die? Message-ID: <430F6828.2070109@mac.com> In-Reply-To: <200508261803.j7QI3J0W071198@himinbjorg.tucs-beachin-obx-house.com> References: <200508261803.j7QI3J0W071198@himinbjorg.tucs-beachin-obx-house.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430F6828.2070109>