I have already made a few contributions to the Wiki,
and whenever someone comes up with a question that is
already documented, I point them to the wiki. I think
it's a wonderful tool!
I've been a Windows (NT/2000/2003) admin for 9 years
now and have done AIX and Linux for 3 years. Windows
does not have a built-in crond; NT had a CLI scheduler
called 'at' and 2000/2003 has a GUI-based scheduler
aptly named Task Scheduler. It's easy to use,
effective and has already been documented in the wiki.
It's in
http://eventum.mysql.org/wiki/index.php/Installation_notes_for_Windows
Contrary to what the author says, it's not an ugly
hack, it's actually the Windows way of doing things.
A MUCH better scheduler is the one that comes bundled
with MS SQL Server, but I understand it's not
available for everybody to use - in fact, even though
it's available at my job (we're mostly an MS shop -
I'm the local open-source pundit and I'm slowly
introducing free software) I'm using Task Scheduler.
Regards,
Georger
--- Joao Prado Maia <jpm@stripped> escreveu:
> Georger,
>
> > If Windows is installed on drive C:\, even though
> > you're CDing to drive D:\ you're still in drive
> C:\.
> > That's because the current directory is assigned
> on a
> > per-drive basis, not per-system - you have to
> change
> > the current drive as well. Try and put a
> >
> > D:
> >
> > before the CD. This should fix things. Regards,
> >
>
> This is a great tip! Are you running the Eventum
> cron scripts through
> crond on Windows? If so, would you mind adding some
> documentation to the
> Eventum Wiki?
>
> It's located at http://eventum.mysql.org/wiki/
>
> --Joao
__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/
