comment on

So - here's the cause for the problem - in case someone else runs into something similar in the future.

The svn.exe binary was included in a directory that has elevated execution rights associated through a policy. The perl binary is not in that same directory, so Win7's kernel refused to run the svn command in the same process space.

Moving the svn binary out of this directory, or moving the perl tree into this directory resolves the problem.

Michael

In reply to Re: Windows 7: fork in perl script spawns new cmd window by mpeppler
in thread Windows 7: fork in perl script spawns new cmd window by mpeppler

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.


go ahead... be a heretic
	PerlMonks