This is my third try. I typed a big reply and posted it, and it
magically disappeared into the void. That's happened to me on another
google group page -- has anyone else seen that?
Anyway, the scheduler is great. I ended up putting the instantiation
and scheduling into a .rb file required from environment.rb, so it
starts up when the application does.
However, that also makes it start up in script/console. I don't want
to have two schedulers' tasks stomping on each other when I run the
server and console at the same time. I could probably use a semaphore
stashed in memcached or the database or something. Does anyone have
other ideas?
Is there any way to stop a particular schedule_every task? Or should I
allocate a scheduler to it and just stop that when I need to?
I did this:
scheduler.schedule_at(Time.parse('18 July 2007 14:09:00')) { puts
"Running the AT job" }
which is very nice. However, it runs at the start of every application
launch, well past the time specified. I consider this a bug, since I'd
like to use it to perform a database action once a month without
having to worry about it repeating with every application restart.
Thanks!
Lee
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenWFEru users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---
