search for: first_run

Ezra, Sorry for inundating the list. In using the autostart, repeat_every, and first_run, I noticed a behaviour I didn''t expect. I would like the job to run starting at 2am, and then every 24 hours. So I set first_run to Time.now.beginning_of_day + 2.hours, and repeat_every to 24.hours. The problem is if backgroundrb starts up at 6am (due to a code change or server bump), th...

If you''re in a timezone with an abbreviation that map to more than one timezone (eg, CST), first_run may not work as you expect it to. Witness: $ irb -r time irb(main):001:0> Time.now => Wed Oct 04 20:37:24 CST 2006 irb(main):002:0> Time.parse(Time.now.to_s) => Thu Oct 05 10:37:30 CST 2006 Notice the 14 extra hours... Time.parse converted the time thinking CST meant -06:00 when my s...

Folks- I just commited another revision of the plugin. Nothing huge in this update but some extra features. Acl lists are now configurable in the config file. So you will want to blow away and recreate your config file again. Thanks to Georg Friedrich for this. And I applied Gunter Ladwig''s patch for singleton worker classes. These are workers that only have one instance of

Hello all, I am interested in using BackgrounDRb to clear out ActiveRecord based sessions. I have this working, just with a small hitch, here is the code: class ClearSessionsWorker < BackgrounDRb::Rails repeat_every 7.minutes first_run Time.now def do_work(args) Session.destroy_all(["updated_at < ?", 20.minute.ago ]) end end It''s not very complicated and does remove sessions, it''s just that once the job is done, the thread hangs out leaving a connection to my database open. After some tim...

I have a simple worker that I set up with repeat_every: class DueNoteQueuerWorker < BackgrounDRb::Rails repeat_every 1.minutes first_run Time.now def do_work(args) @logger.debug("Sending due notes. The current time is #{Time.now}") end end I want this to run every minute, all the time. The first run is fine, but it seems that subsequent runs get executed twice. From the logfile: # Logfile created on Mon A...

...about the following simple application using autostart and repeat_every. A thread(?) is forked for processing task at first, but at sencond time two threads seem to be forked. My simple application code is... - In worker class class FooWorker < BackgrounDRb:Rails repeat_every 2.minutes first_run Time.now def do_work puts Time.now.to_s + "Start processing....." do_some_task() puts Time.now.to_s + "Finish processing" end - In background.yml autostart: 1: class: foo_worker arg: '''' Result is.... --- First time--- St...

Hey. I have a very annoying problem, and was wondering what is wrong. Suppose I have backgroundrb running, and then I have an action in some controller. In the action I define a worker. When leaving the action, suddenly the connection to backgroundrb is lost: DRb URI: druby://localhost:22222 Pid: 3976 Autostart... done druby://localhost:42531 - #<Errno::EBADF: Bad file descriptor -

...Fair enough. All is working beautfiully and this is the perfect candidate for using with backgroundRb. First couple of runs through it worked perfectly. Then things started going wonky. My worker is as simple as this.. class FilemakerSyncWorker < BackgrounDRb::Rails repeat_every 20.minutes first_run Time.now def do_work(args) Syncer.new.synchronise end end What''s really weird, and maybe is my complete lack of understanding of threads and such like is this, randomly, throughout the day the log records created in .synchronise are getting *almost* duplicated, it''s like...

Is there something special I need to do to access session data in a worker? I''m using an AR session store. I''ve been working with Ezra''s tutorial, modifying it a little here and there to figure it out. So I changed the progress bar to a simple count-down in the worker which sends back the count to display in the view. No big deal. But if I try to access session

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as

This patch series is based on the VM introspection patches (https://lore.kernel.org/kvm/20200721210922.7646-1-alazar at bitdefender.com/), extending the introspection API with EPT Views and Virtualization Exceptions (#VE) support. The purpose of this series is to get an initial feedback and to see if we are on the right track, especially because the changes made to add the EPT views are not small