in reply to Text File Busy - or not?

Doing a google search for, "CGIWrap error text file busy", I found:
This message usually indicates there is a problem with the script itself. Often this indicates either that the #! line of the script is incorrect, or the script was uploaded in binary mode instead of ascii mode. Check to make sure that the script does not have control-M's at the end of every line. This is typically a problem if the script was edited or uploaded from a DOS/Windows/Macintosh station to a unix based server.
HTH,
Chris

Replies are listed 'Best First'.
Re: Re: Text File Busy - or not?
by freddo411 (Chaplain) on Jun 26, 2003 at 18:01 UTC
    It helps a lot if you have shell access to the machine where the script resides. If you do then:

    To see if you have extra line end characters:
     vi <script name>
    you'll see a ^M at the end of each line. To quit vi:
     <esc>:q!

    To fix this (on many unix flavors):
     dos2unix <script name> <script name>

    Uploading the file in "text" mode in some ftp clients will automatically convert the line enders for you when performing an upload/download. Note that some ftp clients DON'T do this, YMMV. Binary mode is /Absolutely Necessary/ if you uploading gifs, jpgs, etc. Some ftp clients have an "automatic mode" which will use what it thinks is the right mode depending on the file extension. Again, YMMV. Cheers

    -------------------------------------
    Nothing is too wonderful to be true
    -- Michael Faraday

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom