Followup On Perl Dumping Core
Tim Daneliuk
tundra at tundraware.com
Fri Jun 18 18:30:47 UTC 2010
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 at tundraware.com
PGP Key: http://www.tundraware.com/PGP/
More information about the freebsd-questions
mailing list