Siep Korteling wrote:
> Peter Bailey wrote:
>> Robert Klemme wrote:
> (...)>
>> I'm very sorry. You're right. I'm on Windows XP, 32-bit. Ruby 1.8.6. The 
>> scheduler I use is Splinterware's System Scheduler. It's set up to only 
>> execute when there are files in the source directory. Like I said above, 
>> the first thing my script does is move the input files. So, it's very 
>> rare that there would be new files in the input directory the next time 
>> it's scheduled. But, even if there were, it should kick off a new 
>> instance of the script.
>> The script executes fine until it gets to the part where it's supposed 
>> to copy and move the files, using FileUtils.
>> It works perfectly in the editor, like I said, and, it works perfectly 
>> when run from the command shell.
> 
> This system scheduler uses the LocalSystem account (by default). Does 
> this account have access to both the source and target folders?
> 
> hth
> 
> Siep

Good point. No, I have it set to use a network account that has rights 
to all necessary drives. It's the user that's auto-logged in on that PC. 
The same user using the editor and the command shell.
-- 
Posted via http://www.ruby-forum.com/.