comment on

You should go to http://www.sysinternals.com/ and grab a tool (like Handle) that will show you who really has the file open. It might be cmd.exe or it might be something else that cmd.exe launches that goes away when cmd.exe's console goes away. Perhaps it is something that you can 'kill' to make working around the problem easier.

There are also other tools that will let you monitor what is going on such that you might be able to figure out how to prevent the problem.

I'd think that Perl would not even leave the script open unless you had a __END__ / __DATA__ in it. If so, closing DATA in your script may prevent the problem (yes, I'm not assuming that cmd.exe is what is keeping the file open at this point).

- tye

In reply to Re: command prompt locks scripts for editing (sysinternals) by tye
in thread command prompt locks scripts for editing by inman

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.


Do you know where your variables are?
	PerlMonks