Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Greetings!

Maybe it is not fully right place to post _this_ question, but, since it is still very related to Perl...

Thanks for the generous help of the monks, I have finally finished my Perl program (a number of scripts), and began testing it remotely. Now, on remote access, I have found a strange bug, that a file, that should be opened by a script to writing

open (IDFILE,"+>$idfile") || die "2. Unable to open $idfile $!\n";

in fact is not opening, despite the command does not produce an error message, and an attempt to print into the file brings to halt of the script execution. The file is in read/write/execute permission mode on IIS server on Windows XP. Is there any way to overcome this (in any case, due to the requirements, I should be able to write into several files)?

Thanks in advance,
Dovkont.


In reply to Files on MS IIS server by Dovkont

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.