Excellent. I'm really liking the scheduler.
I put the scheduler instantiation and setup in environment.rb
(actually a separate file that gets required from environment.rb) so
that it gets launched at application startup.
The problem with that is that the scheduler runs in script/console as
well as script/server. I wouldn't want two schedulers' activities
stomping on each other if I'm in console while the server's running. I
suppose I could set a semaphore in the database... Anyone have other
ideas on this?
Also, I did this:
scheduler.schedule_at(Time.parse('18 July 2007 14:09:00')) { puts
"Running the AT job." }
It displays "Running the AT job." at every application run, even well
after the specified time. Is this desired behavior, a bug, or merely
unspecified behavior? I can see why it would happen, but to my mind
it's a bug. I'd like to schedule certain database operations to happen
once, which I felt schedule_at would give me.
Oh, also #2: Is there a way to stop a given schedule_every? Would I
need to use a separate scheduler to do that, and just stop the
scheduler itself?
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
-~----------~----~----~----~------~----~------~--~---
