I've seen those symptoms when (in the name of security) the hoster moves the apache into chroot, then installs just what he thinks he needs into that chroot.

I even had to deal with that once, running the script, seeing what broke, copying the missing file from the normal install into the chroot, running the script (lather, rinse, repeat).

The hoster insisted this was the only way to have his apache instalation as secure as possible. Of course, three weeks later, his boss wanted a web-based forum - and that beast needed a whole bunch of modules, so the guy cd'ed into the chroot and installed the complete perl there. Seems perl wasn't so dangereous when he had to work with it.

In reply to Re: Re: can't locate CGI.pm ... by matija
in thread can't locate CGI.pm ... by vincentberenz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.