Thanks for the idea Wrex, but that wasn't it. It was the Schedule service's requirement for local Administrator access rights.
I am using the /interactive switch though, as I like to see the Perl activity happen in a CMD window.
I was recently caught out by running a PERL script that opened a file but had an error and was waiting for me hit return before altering the file and closing it.
I mistakenly called the script via the AT command, without the /interactive switch, and couldn't for the life of me work out why the file was always locked and the script would not run again unless I rebooted.
The script was waiting, invisibly, for me to hit return.
I now never call a Perl script via AT without the /interactive switch unless I am POSITIVE that it is bug-free.
-
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.
|