Date: Sat, 19 Jun 2010 09:29:23 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Followup On Perl Dumping Core Message-ID: <4C1CD443.1000303@tundraware.com> In-Reply-To: <4C1BCCCA.7090503@tundraware.com> 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> <4C1BCCCA.7090503@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/18/2010 2:45 PM, Tim Daneliuk wrote: > 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. > It would seem that this was the problem. Clearing out the old contents of .spamassassin made the perl SEGVs stop... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C1CD443.1000303>