If the server that this cgi script is running on is a linux box, you damn well better not use backslashes at all in the path names for input or output files. As for setting permissions, the only thing you need to worry about is that the "user" account that is the web server has read+execute permission at each directory layer above the directory where file will be stored; and it must have read+write+execute on the storage directory.

If the storage directory is owned by the web server user account, its permission can be 755; if it's owned by some other user, but has group ownership that matches the web server's group, then it can be 775. As for permissions on the files that are created, that's up to you.

In reply to Re^2: Cannot open files using CGI by graff
in thread Cannot open files using CGI by MonkPaul

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.