in reply to Broken perl install

First, this is the worst Perl installation that I've ever seen. If I hadn't seen it with my own eyes, I wouldn't have believed it!

Second, it's not a Perl problem nor a Redhat problem. You need to work on your computer skills.

Third, don't try to salvage it. It's totally useless as is.

Fourth, backup your work, reformat the disk, then reinstall Redhat.

Good Luck!

Replies are listed 'Best First'.
Re^2: Broken perl install
by billie_t (Sexton) on Aug 06, 2006 at 23:45 UTC

    It turns out that perlivp has a similar output after a FRESH build of RedHat Linux EL 4 (did a full server rebuild as a last resort). Obviously either perlivp or some of Perl itself is broken on RHEL4, which makes it hard to diagnose if Perl gets really broken by a subsequent module install.

    Got a support call in with RedHat for this issue.

Re^2: Broken perl install
by billie_t (Sexton) on Jul 30, 2006 at 04:04 UTC

    Hm, since the server is working fine except for certain Perl scripts (not all), it's mainly a Postfix server which is still delivering enterprise mail successfully, and that this problem wasn't happening until I installed a big bunch of modules, that comment isn't particularly helpful. I'd love to know which "computer skills" I'm supposed to be improving here (although I'll cop to the "install only ONE thing a time" issue).

    I don't pretend to be a Linux expert, but it concerns me that installing modules means "reformat your server". And people bitch about Windows.