Date: Fri, 18 Jun 2010 13:56:26 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Followup On Perl Dumping Core Message-ID: <4C1BC15A.5020301@tundraware.com> In-Reply-To: <4C1BC075.4030903@tundraware.com> References: <4C1BB9D9.10704@tundraware.com> <4C1BBA99.9010705@gmail.com> <4C1BBB4E.8080907@tundraware.com> <4C1BBC19.8030007@gmail.com> <4C1BC075.4030903@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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-after-upgrade. >>> Wouldn't the 'portupgrade -f *' take care of this, or should I go run the >>> script now, "just in case"? >>> >> >> portupgrade does not do this for you. If you don't remember, I'd >> suggest running it. >> >> Regards, >> > > > Well, I just did, and it reports no changes were necessary... > I should mention that I don't think it is actually "dumping core". It's just reporting the problem in /var/log/messages... -- ---------------------------------------------------------------------------- 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?4C1BC15A.5020301>