Hi there, I''m just working on getting backgroundrb (1.0.1) up and running. I''m no expert with ruby, etc, so I still don''t quite get a few things. I have scheduled workers that run every few minutes. That works fine. I have other workers that run once per day or even once per week. It doesn''t make sense to have them running all the time. I''d rather they just fire up when the time comes and shut down again. I thought I could "set_auto_load true" and that they would be started up when the schedule dictated. Then I''d use "exit" at the end to stop them again. But apparently, the schedules only work on running workers. What am I missing? What''s the best way to handle workers that only need to take action once per day and therefore don''t need to be running all the time? Thanks, Scott
Hi Scott, On Jan 26, 2008 4:02 AM, Scott Ward <scott at shefield.com> wrote:> Hi there, > > I''m just working on getting backgroundrb (1.0.1) up and running. I''m no > expert with ruby, etc, so I still don''t quite get a few things. > > I have scheduled workers that run every few minutes. That works fine. I > have other workers that run once per day or even once per week. It doesn''t > make sense to have them running all the time. I''d rather they just fire up > when the time comes and shut down again. > > I thought I could "set_auto_load true" and that they would be started up > when the schedule dictated. Then I''d use "exit" at the end to stop them > again. > > But apparently, the schedules only work on running workers. > > What am I missing? What''s the best way to handle workers that only need to > take action once per day and therefore don''t need to be running all the > time?Currently you can''t. You will have to let the worker running, but if you can bear with us for few weeks, I am working on getting a new release of bdrb out of door and it will have this feature. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org
On Sat, Jan 26, 2008 at 4:49 AM, hemant <gethemant at gmail.com> wrote:> Hi Scott, > > > On Jan 26, 2008 4:02 AM, Scott Ward <scott at shefield.com> wrote: > > Hi there, > > > > I''m just working on getting backgroundrb (1.0.1) up and running. I''m no > > expert with ruby, etc, so I still don''t quite get a few things. > > > > I have scheduled workers that run every few minutes. That works fine. I > > have other workers that run once per day or even once per week. It doesn''t > > make sense to have them running all the time. I''d rather they just fire up > > when the time comes and shut down again. > > > > I thought I could "set_auto_load true" and that they would be started up > > when the schedule dictated. Then I''d use "exit" at the end to stop them > > again. > > > > But apparently, the schedules only work on running workers. > > > > What am I missing? What''s the best way to handle workers that only need to > > take action once per day and therefore don''t need to be running all the > > time? > > Currently you can''t. You will have to let the worker running, but if > you can bear with us for few weeks, I am working on getting a new > release of bdrb out of door and it will have this feature.Scott, can you file a ticket regarding this, on : http://backgroundrb.devjavu.com/ ?/