With this much grief, I would have changed providers long before now ...

That said, you probably want use lib './lib'; if the lib directory is in the same place you keep your CGIs.

That should even work in a chrooted environment, but if it doesn't I suggest some careful probing of where your scripts think they are and what they can see.

Something like...

#!/usr/bin/perl use CGI::Carp qw( warningsToBrowser fatalsToBrowser ); use Cwd qw( getcwd abs_path ); use lib qw( /some/where ); $|++; print "Content-Type: text/plain\n\n"; print "Current directory is ", getcwd(), "\n\n"; foreach my $path ( @INC ) { print $path, " -> ", abs_path($path), "\n"; }

... but adding other checks (like permissions) wouldn't go amiss either.

    --k.



In reply to Re: Re: Re: How do I...Redirect error.log data to a file of my chosing by Kanji
in thread How do I...Redirect error.log data to a file of my chosing by S_Shrum

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.