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 repor
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'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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'l
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
> proce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 w
On 6/18/2010 1:52 PM, Tim Daneliuk wrote:
> On 6/18/2010 1:34 PM, Glen Barber wrote:
>> On 6/18/10 2:30 PM, Tim Daneliuk wrote:
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
On 6/18/2010 1:34 PM, Glen Barber wrote:
> On 6/18/10 2:30 PM, Tim Daneliuk wrote:
>>> 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 *'
On 6/18/10 2:30 PM, Tim Daneliuk wrote:
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
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
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 r
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 associa
11 matches
Mail list logo
