A common problem in situations where you don't have shell access, and have to upload CGI scripts and data files via FTP, is that things aren't where you think they are when the script executes.

One brute-force way of determining what is there is to upload a test CGI that does

use Cwd; print "Content-type: text/plain\n\n"; print getcwd(), "\n\n"; opendir(DIR, ".") or die ".: $!"; print join("\n", readdir(DIR)), "\n"; closedir(DIR);
The will tell you where the script thinks it is when executing, and what else is there. You may find that you need to either chdir() or use an absolute path to open data files that reside elsewhere.


In reply to Re: Files on a Win2000 server by dws
in thread Files on a Win2000 server by XeneX

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.