From: bdezonia@...
Date: 2007-11-08T07:45:02+09:00
Subject: Re: Windows: Scheduled Ruby script won't run

On Nov 7, 1:27 pm, Mohit Sindhwani <mo_m...@onghu.com> wrote:
> Mohit Sindhwani wrote:
> > The most common problem is the path.  I usually bootstrap my Ruby
> > script using a .cmd file that sets the path to my Ruby interpreter and
> > then calls the interpreter with the name of the script.  It's always
> > worked for me.  Also, if for some reason, you don't trust the Windows
> > scheduler, you could use PyCron - it's a cron replacement on Windows
> > that works very well (specially recommended if you plan to schedule
> > the script more frequently than just system startup).
>
> *snip*
>
> the other problem could be related to 'require' - if you require a file
> that is in your local directory and not in a system standard path, you
> will run into problems.  You'll need to change directory to the
> directory where your scripts are before you do the require.
>
> Hope this helps.
>
> Cheers,
> Mohit.
> 11/8/2007 | 3:27 AM.

Awesome idea Mohit (thanks!) but it does not work for me. The .rb
script will launch via a .cmd file from a command prompt. Now when I
try to start a scheduled task it at least does something. It returns
an error code of one. My file that is written to by the first line of
the script every time it is launched does not show any record of the
program actually being launched. And I did not see either the .rb file
or the ruby.exe show up in task manager (or any .cmd file either). The
only require statement refers to 'net/smtp'. Any more ideas?