> We want it to run once per day at a specified time. It runs on a Windows
Server 2003 box. Windows Scheduler is very flaky on this box -- sometimes
it runs the script, sometimes not. When it does run the script, it runs as
expected.
I've had this problem on every windows box. Have task schedul
Michael,
I use the WS (Windows Scheduler) extensively on several machines many
times daily. I have scripts that run every 15 minutes, 30 minutes,
hourly, daily, monthly, etc. I find I get the best mileage from creating
a batch-file that contains the execution of the program and its
parameters and
The only thing I can think of is that the script is running from scheduler
with some funky/wrong username that is not allowed to see the output file
with -f. I would check that. For cron usage I've used wincron to run
expect scripts with no problems. U can get it from Tucows.
At 10:50 AM 8/24/0
* On 2005:08:24:10:50:34-0500 I, Michael D Schleif <[EMAIL PROTECTED]>, scribed:
> Here is the first point of breakage in the code:
>
> -f $out_file
> or die "\n\tERROR: *NOT* a file: \'$out_file\'\n\n";
>
> I have simplified this, with same failure:
>
> -f $out_file and die;
