similar to: scheduling jobs

Hello all, I''m new to Ruby and have come across this project that seems to be the most mature scheduling project for Ruby. I''ve had some brief experience with Quartz for Java and was wondering if there were any plans to provide an option to save scheduled jobs into some sort of data store? If not, is that something the project would be interested in? Has someone

I''m very interested in using backgroundrb for running jobs every n minutes. The release notes say that this functionality is not yet ready via backgroundrb. But I wonder, can I call backgroundrb with a ruby script from cron ? I know I could create a cron job that calls lynx (or whatever) on a specific page that will call backgroundrb, but I want to know if there other

I''ve scheduled cron jobs etc before, but I''m curious as to how to layout a worker properly. Here''s a basic example of what one of my workers looks like: class FooWorker < BackgrounDRb::MetaWorker set_worker_name :foo_worker def create(args = nil) logger.info("Starting test: #{Time.now.strftime("%T")}") run_test logger.info("Finished test:

I have BackgrounDRb configured to handle two cases of long-running tasks: (1) on-demand user triggered requests for some action, and (2) scheduled background running of tasks on a predetermined schedule. In my particular case, we have a publication task that can take several minutes to perform. Users can setup a regular publication schedule, or can hit a ''publish now'' button to

I''m running a fresh checkout of release 1.0.1 ... It''s now 11:32 am local time on January 31. I''ve configured a single worker for a test. If I use the following schedule in my background.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following

Hi , How do i schedule a job that can send emails at intervals of time using backgroundrb and rails For testing When i hit the controller i''m able send the emails. but that is not i intend to do ..... I want to use backgroundrb and rails in which i''ll schedule a job for every 5 minutes/ 1 minute or so..... to send an email But when i write

Hi all, I''ll attach a new version zfs-auto-snapshot including some more improvements, and probably some new bugs. Seriously, I have tested it, but certainly not all functionality, so please let me know about any (new) problems you come across. Except from the change log: - Added support to schedule using at(1), see README.zfs-auto-snapshot.txt - take_snapshot will only run if

I''m a big "fan" of BackgroundRB ... 1.0 came along just when my project needed it, and I''ve been very happy. Thanks much for this very helpful piece of software. My question: I have a worker scheduled cron-style as follows: :notification_worker: :notify: :trigger_args: 0 0 8 * * 1,3,5 * I.e., I want to run this particular worker method at 8:00a

I''ve been using backgroundrb since back in March 2007 or so. It''s been working mostly OK for me, but since the old version doesn''t seem to work out of the box with rails 2.0 for me, I decided to test out the latest version. So, I''m looking at the scheduling, and trying to figure out the best option for what I want to do. What I have is a set of workers that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i''m trying desperately to schedule some worker methods within rails 2.0.2. The problem is, both methods don''t even get called by BackgrounDRb. my background.yml: > --- > :backgroundrb: > :port: 11006 > :ip: 0.0.0.0 > --- > :schedules: > :server_worker: > :update: > :trigger_args: 1 *

I noticed in the BackgroundRB class in the delete_worker method there is a line: if @jobs[key].respond_to? :thread For some reason this is returning false for me, it gets down to this line and returns false, not killing the thread. Any idea why this is returning false? Thanks for your help. Thank You, Ben Johnson E: bjohnson at contuitive.com -------------- next part -------------- An

I wrote the following script to run garbage collection on Backgroundrb workers older than 30 minutes: class WorkerCleaner def self.remove_stale_workers MiddleMan.gc!(Time.now - 60*30) end end I stuck is under /lib in my Rails app and run it using script/runner from a cron job. The only problem I''m seeing is that this script kills my backgroundrb_results and backgroundrb_logger

I need to run the same worker''s method twice per day with different arguments. Unfortunately, only the second entry in the schedule is firing. I created an experimental worker to verify this: Worker: class ExperimentWorker < BackgrounDRb::MetaWorker set_worker_name :experiment_worker def create(args = nil) # this method is called, when worker is loaded for the first time

I use BDRb to process RSS feeds for users on my site (http://feedflix.com). I have a batch job that queries the DB for records that haven''t been updated in the last so many hours and kicks off a background job for each of them. If N records are returned by the DB, N background jobs gets queued and get done serially. As long as N is 255 or under, everything works like a charm.

Hi Folks, BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be used with Ruby on Rails applications for offloading long-running tasks. Since a Rails application blocks while serving a request it is best to move long-running tasks off into a background process that is divorced from http request/response cycle. This new release of BackgrounDRb is also modular and can be used

Hey all, I''ve come accross BackgrounDRb and I have to say it''s a wounderful piece of software. It has the potential to solve so many of the problems that I am facing with a current RoR project. Like many others I was having issues with the scheduling side of things, I noticed that hemant said there was a new version coming out. So I checked out the version from trunk, and have

There is a line in the backgroundrb codebase: sleep 0.1 # TODO this is dangerous; could skip over some jobs Could this explain why my scheduler stops triggering? It only seems to work for about 12 - 24 hours before schedules are being skipped... Once I changed the times to using cron trigger in backgroundrb_schedules.yml and set the times to every 37th and 59th minute of the hour, instead of

Cc''ing to the list for archival purposes: On Tue, Mar 25, 2008 at 7:55 PM, Brian Noguchi <brian.noguchi at gmail.com> wrote: > Hi Hemant, > > I''m Brian Noguchi, a developer in the Bay Area. I have some questions about > backgroundrb, and I found your contact info on a forum. I figured its > probably best to get answers straight from the source. > >

I''m running the latest backgroundrb mainly for scheduled tasks support. As per the documentation I created the backgroundrb_schedules.yml with the following: simple_label: :class: :document_sorter_worker :worker_method: :do_work :job: :bleh :trigger_args: :start: <%= Time.now + 5.seconds %> :end: <%= Time.now + 10.minutes :repeat_interval: 1.minute Under

I''ve been having a terrible time with the backgroundrb scheduler. The issues I''m having is that the scheduled actions aren''t ran at all and if they do, the process stays around forever. I''m using the backgroundrb as a nightly cron to run some accounting operations. questions: 1. How can I have the process destroyed after the worker completes? 2. Any idea on