similar to: Minor Release

Howdy Folks- I''m happy to announce a new release of BackgrounDRb! I have added quite a few new features and included some nice patches from folks on the list. $ script/plugin install svn://rubyforge.org//var/svn/backgroundrb All of the code now stays within the plugin and the start and stop scripts are now just stubs. This makes it easier to tweak or figure out how it works.

Hey Folks- I have just pushed a new release of BackgrounDRb to rubyforge. It has some nice new features to allow for usage of your ActiveRecord Models within your worker classes. I also added a config file for setting hosts and ports and if you want to load rails or not. Please have a look and let me know if anyone runs into any issues. If you already have an older version installed then you

Hey Greg- Yes I am sorry, the new architecture uses fork and named pipes and a bunch of unix stuff to do its magick. Now you may be able to port it to qwork on windows, but I don''t think it is possible :( I''m really sorry about this but I need this thing to be as robust and solid as it can be and in the end windows isn''t compatible. Now you may be able to

I''m trying to use BackgrounDRb to do image processing on large uploaded zip files of images, but $script/plugin install svn://rubyforge.org//var/svn/backgroundrb gives me this: /usr/lib/ruby/1.8/open-uri.rb:88:in `initialize'': No such file or directory - svn://rubyforge.org//var/svn/backgroundrb (Errno::ENOENT) I can install the old version with $script/plugin install

Hi, I''ve been using backgroundrb with some success up to now, but now when I do the start or setup tasks they just fail silently. Nothing in the log, no .pid file, and nothing in the process list. Rake with -trace just says, ** Invoke backgroundrb:setup (first_time) ** Execute backgroundrb:setup Any hints on how I can get more verbosity, or thoughts on what might be happening? (This

Friends- There is a new release of BackgrounDRb. This time it is a full fledged rails plugin with generators and rake tasks thanks to Saimon Moore. Thanks Saimon! You can read all about it here on my blog: http://brainspl.at/articles/2006/05/25/backgroundrb-new-release The newest feature besides the much cleaner way to install and control the drb server is caching. You can now use

Hey Folks- I have just pushed a new release of BackgrounDRb to rubyforge. It has some nice new features to allow for usage of your ActiveRecord Models within your worker classes. I also added a config file for setting hosts and ports and if you want to load rails or not. Please have a look and let me know if anyone runs into any issues. If you already have an older version installed

Hi the list people, hi Ezra, I just read from this message http://rubyforge.org/pipermail/backgroundrb-devel/2006-July/000134.html that BackgrounDRb will offer a way to kill a worker from within itself. As this message is from 7/25, I wonder if this feature has been added since. If not, is there any way to do it? I tried this: MiddleMan.delete_worker(@_job_key) But it raise: uninitialized

It''s that time again friends. skaar has been at it again and has greatly improved the stability of the new system. And Ara Howard has helped a ton by working with us on the slave library to iron out the wrinkles./ The results is a lot nicer backgroundrb for everyone. I have to say another huge thanks to skaar. He has singlehandedly wrote almost all of this new version and many

Hello, Bravo Ezra for Backgroundrb! What an elegant piece of engineering. I envision many folks like myself looking at our CPU hogging executables and finally seeing a clean path to the Web. I was wondering if any folks have a good strategy for calling out to a C++ (or any other compiled) executable from a worker. Is the only option to call system() from a worker? That feels a bit unsatisfying.

Hi all My problem is that: With reference to http://backgroundrb.rubyforge.org/ 1---I have download backgroundrb from http://opensvn.csie.org/ezra/rails/backgroundrb to my vendor/plugin in my application folder. 2-- after that I used the command to run :-rake backgroundrb:setup -- trace From my application

Folks- I just pushed out a new release last night. THis is a bug fix release as well as some new features that have come up that people need. I made the MiddleMan class include Singleton so it is now a true singleton. What this means is that the autostart stuff now works correctly because you can always get the same MiddleMan instance from anywhere within the drb server including your

I''ve created a couple of tasks in my deploy.rb file for starting and stopping backgroundrb on the remote server. The stop task runs fine and kills the process. And the start task *seems* to run successfully, but backgroundrb is never started on the remote host. Has anyone had success with this? Here are my deploy tasks: desc ''Start backgroundrb server (default

I''m using backgroundrb to periodically download a large file via ftp from a remote location and then import it into the database. To perform the import, I was using the following: ActiveRecord::Base.connection.execute(%{load data infile ...;}) although on a file with 2.5 million records, this can take 5 minutes, which seems to tie up my rails application while this executes (even

this: Index: script/backgroundrb/lib/backgroundrb.rb =================================================================== --- script/backgroundrb/lib/backgroundrb.rb (revision 16) +++ script/backgroundrb/lib/backgroundrb.rb (working copy) @@ -29,7 +29,11 @@ # the log via @logger def initialize(args) @logger = BACKGROUNDRB_LOGGER - Thread.new { do_work(args) } +

OK I know whats happening. Your while loop completes and calls kill on the worker before your task_progress controller method ever gets called> So the worker is deleted and when you try to access it from rails you get an error because there is no longer a worker at that job key. The kill method is meant to be used within a worker that you fire and forget. If you want to get the

Begin forwarded message: > From: Ezra Zygmuntowicz <ez at brainspl.at> > Date: June 29, 2006 8:18:10 PM PDT > To: Douglass Turner <douglass.turner at gmail.com> > Subject: Re: [Backgroundrb-devel] Need to send email from a worker > > > On Jun 29, 2006, at 7:45 PM, Douglass Turner wrote: > >> Hello, >> >> Can someone suggest the simplest way to

Hi all, BackgrounDrb was exactly what I needed for a project I''m working on at work. Everyone''s really impressed, and now it''s time to put the system into production. My question is, how do I avoid having to manually run the startup and shutdown scripts (or the rake tasks) for backgroundrb? I tried putting a system "rake backgroundrb:start" in my

Hi all (and Ezra), I couldn''t get my rake tasks to work after installing the plugin -- until I added a line at top of to test_helper.rb: require File.expand_path(File.dirname(__FILE__) + "/../script/backgroundrb/lib/backgroundrb.rb") Is this in the docs? -- Charles Brian Quinn www.seebq.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sep 14, 2006, at 10:25 AM, Michael Siebert wrote: > Hey Ezra, > how is the status of your worker pool? i need some thing like this > ASAP and i can''t get David Lemstra''s QueueWorker to work, so: whats > the status? do you have some "beta" lying around on your hard > drive? I dont want to spend my time on that if you''re coming up >