Date: Wed, 16 Jun 2010 09:32:05 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Perl Dumping Core Message-ID: <4C18E065.8020105@tundraware.com> In-Reply-To: <4C18DD2B.6060408@infracaninophile.co.uk> References: <4C18DB83.50902@tundraware.com> <4C18DD2B.6060408@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/16/2010 9:18 AM, Matthew Seaman wrote: > On 16/06/2010 15:11:15, Tim Daneliuk wrote: >> I am running 8.1-PRERELEASE and seeing a half dozen of these a day: > > > >> (perl5.10.1), uid 0: exited on signal 11 > > >> Anyone have theories on this? > > You have a perl process or processes owned by root that are dying due to > segmentation violations. > > Unfortunately, we don't do omniscience[*] or clairvoyance or anything > like that, so unless you give us some useful information to work with, > that's literally all we can tell you. 'Sorry, I wasn't more specific :) And I DO expect you do be omniscient BTW, after all, my users/clients expect ME to be ... > > Start by inspecting the output of ps(1) to find likely looking perl > processes. If you've actually got perl.core files you may be able to > investigate with a debugger and work out what is producing them, but I > wouldn't hold out too much hope of that. > > Cheers, > > Matthew > > [*] well, only occasionally. > It seems that the long running perl processes are there in support of Mailman. I know it periodically restarts itself but I don't know how gracefully it shuts down the perl processess ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C18E065.8020105>