From owner-freebsd-questions@FreeBSD.ORG Fri Jun 18 19:45:23 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96D9F1065670 for ; Fri, 18 Jun 2010 19:45:23 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 3697B8FC15 for ; Fri, 18 Jun 2010 19:45:23 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id o5IJjFxA008739 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 18 Jun 2010 14:45:15 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4C1BCCCA.7090503@tundraware.com> Date: Fri, 18 Jun 2010 14:45:14 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: FreeBSD Mailing List References: <4C1BB9D9.10704@tundraware.com> <4C1BBA99.9010705@gmail.com> <4C1BBB4E.8080907@tundraware.com> <4C1BBC19.8030007@gmail.com> <4C1BC075.4030903@tundraware.com> <4C1BC15A.5020301@tundraware.com> <4C1BC454.4060505@infracaninophile.co.uk> <4C1BC73B.1030400@tundraware.com> <4C1BCA27.5090702@FreeBSD.org> In-Reply-To: <4C1BCA27.5090702@FreeBSD.org> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (ozzie.tundraware.com [75.145.138.73]); Fri, 18 Jun 2010 14:45:15 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: o5IJjFxA008739 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: Followup On Perl Dumping Core 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, 18 Jun 2010 19:45:23 -0000 On 6/18/2010 2:33 PM, Greg Larkin wrote: > Tim Daneliuk wrote: >> On 6/18/2010 2:09 PM, Matthew Seaman wrote: >>> On 18/06/2010 19:56:26, Tim Daneliuk wrote: >>>> I should mention that I don't think it is actually "dumping core". >>>> It's just reporting the problem in /var/log/messages... >>> You'll only get a core file if the current working directory of the >>> process is writable by the process. Normally. There are various >>> sysctls you can use to affect core-dumping: >>> >>> kern.corefile: process corefile name format string >>> kern.coredump: Enable/Disable coredumps >>> kern.sugid_coredump: Enable coredumping set user/group ID processes >>> >>> See core(5). It is possible to set kern.corefile to an absolute path -- >>> eg /tmp/%N.core -- to always record corefiles in a writable directory. >>> Also, look at setrlimit values for the maximum size core file permitted. >>> >>> Cheers, >>> >>> Matthew >>> > > >> Well ... I've figured out what's causing it, but I still don't know why. This >> is caused when '/usr/local/etc/rc.d/mailscanner restart' is issued from a script >> I run to reset the mail system. However, it does not happen every time ... go >> figure. > > Hi Tim, > > I apologize if you mentioned this before, but are you using Spamassassin > with mailscanner? This message describes a problem that sounds very > similar to yours, and there's a solution included: > http://old.nabble.com/Re%3A-amavisd---exited-on-signal-11---FreeBSD-8-with-Perl-5.10-p28627858.html > > Hope that helps, > Greg Aha! Der plot thickens. I am indeed running SA. I've just clobbered /root/.spamassassin/* This may well be the issue ... Many thanks. ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/