From owner-freebsd-current Thu Oct 22 09:00:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14506 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:00:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14488 for ; Thu, 22 Oct 1998 09:00:14 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA19074; Thu, 22 Oct 1998 08:59:07 -0700 (PDT) (envelope-from jdp) Message-Id: <199810221559.IAA19074@austin.polstra.com> To: grog@lemis.com Subject: Re: sendmail dying with SIGSEGV? In-Reply-To: <19981022174520.V1219@freebie.lemis.com> References: <19981022174520.V1219@freebie.lemis.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 22 Oct 1998 08:59:07 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981022174520.V1219@freebie.lemis.com>, Greg Lehey wrote: > Since today, I've had repeated cases of the sendmail daemon dying with > a SIGSEGV. In each case, it's a child process: the parent daemon > continues to run. This is a 3.0-RELEASE kernel compiled 5 days ago. > I tried recompiling sendmail with debug symbols, but I can't find any > core dumps. Does it not leave one under these circumstances? Can I > change its mind? You can set the sysctl variable "kern.sugid_coredump" to 1. That's kind of a blunt instrument, though, since its effect is systemwide. You can also change "kern.corefile" to make it put the core dumps into a fixed directory, no matter where the process was executing when it died. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message