Date: Fri, 18 Jun 2010 13:30:38 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Followup On Perl Dumping Core Message-ID: <4C1BBB4E.8080907@tundraware.com> In-Reply-To: <4C1BBA99.9010705@gmail.com> References: <4C1BB9D9.10704@tundraware.com> <4C1BBA99.9010705@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/18/2010 1:27 PM, Glen Barber wrote: > Hi, > > On 6/18/10 2:24 PM, Tim Daneliuk wrote: >> I have rebuilt world to today's 8.1-PRERELEASE sources >> >> I have forced a rebuild of every port on the system with: >> >> portupgrade -f * >> >> I have rebooted. >> >> I am still seeing these log messages: >> >> (perl5.10.1), uid 0: exited on signal 11 >> >> The long running perl processes on this system are associated with >> MailScanner. MailScanner does periodically restart itself thereby >> killing these perl processes, but I wouldn't expect this to throw a >> signal 11... >> >> >> Ideas anyone? >> >> > > Have you recently upgraded perl without running perl-after-upgrade > afterwards? > I did upgrade perl some time ago. I do not recall if I ran perl-after-upgrade. Wouldn't the 'portupgrade -f *' take care of this, or should I go run the script now, "just in case"? Thanks, -- ---------------------------------------------------------------------------- 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?4C1BBB4E.8080907>