similar to: disable logging messages to development.log

is there an easy way to disable logging to backgroundrb_debug.log? Regards - reynard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080102/195dee18/attachment.html

Seems this mail did not make it to the list for some reason. It contains my solution for the problem with login_engine without having to load the whole Rails environment. Begin forwarded message: > From: G?nter Ladwig <gladwig at gmx.de> > Date: 22. Juni 2006 23:51:18 MESZ > To: backgroundrb-devel at rubyforge.org > Subject: Re: [Backgroundrb-devel] Models and Backgroundrb

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

Hi, all. Just wondering if anyone has tried using the Paperclip file upload plugin with Backgroundrb. My current implementation uses attachment_fu - I save the file initially to the file system without generating thumbs, then a bdrb process picks up that file, generates thumbs, and saves to S3. This works fine and dandy, the only hitch is I want to save image metadata in the same table

Hey again, After playing with BackgrounDRb a bit longer, I have two more issues I''d like to bring up with it. 1. Logging... it seems like even when the environment is set to production in both Mongrel and the backgroundrb.yml file, all ActiveRecord SQL statements are written to the development log. If you''re doing a lot of ActiveRecord stuff in your workers, then the

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 All, I have this small doubt. Does backgroundrb have anything to do with dispatch.fcgi? some dispatch.fcgi are taking memory as much as 186 MB .... this is monstrous man... Also, if i put load rails environment with backgroundrb.yml file to be false.What will happen? i just loses access to db through ActiveRecord right? I can still use normal mysql gem to access db and modify the

I''m running the latest from svn (rev 285). I''ve been having a problem launching a process repeatedly. What happens is that I get a debug message "some read error" and then the worker refuses to run again. I''ve stripped my worker down to just doing a puts and it still happens. Like the other threads I want to launch my workers as needed, however I get the

The last question from Hemant raised this one for me: Is there a way to use the breakpointer with BackgrounDRb? I tried to set breakpoints inside of a worker but nothing happens in the breakpointer. As they are two different standalone servers, maybe they can''t communicate? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Sorry for attaching patches in emails to the mailing list, but I''m still unable to login to Devjavu for Backgroundrb (I''m able to login just fine for Merb''s Devjavu and submitted a ticket successfully). Anyway, I encountered a bug when trying to #ask_status of a worker before it''s run (or rather, before its result_hash has been set to something). Not sure why

Hi, I am currently working on a project that requires multiple rails applications (lets call them consumers, since they will consume requests) to exposes long running services that will be executed from a management rails application (the producer of the requests). To do this BackgrounDrb was installed on all the consumers and the producer. BackgrounDrb was configured to on each of the consumers

Quick question: If I want to schedule different worker methods defined in the same worker to trigger at different times, is this possible? Would the following scheduler yaml work? :schedules: :foo_worker: :worker_method: method1 :trigger_args: 0 */10 * * * * * :job_key: some_key_1 :foo_worker: :worker_method: method2 :trigger_args: 0 */15 * * * * * :job_key:

Is there a convention for handling exceptions within BackgrounDRb workers? For example, I have a worker which does some asynchronous data processing (*not* a scheduled worker) based on some things in the database. However, if an exception is raised within that worker, then the process for that worker is killed off. Ideally I would want that worker to just silently fail and be optimistic that it

Hello ! 1) I have this error logged by bdrb: undefined method `send_request'' for nil:NilClass framework/packet_master.rb:58:in `ask_worker'' backgroundrb/server/master_worker.rb:59:in `process_work'' backgroundrb/server/master_worker.rb:16:in `receive_data'' backgroundrb/framework/bin_parser.rb:29:in `call'' backgroundrb/framework/bin_parser.rb:29:in

Ezra et al: I have this problem: http://rubyforge.org/pipermail/backgroundrb-devel/2006-December/000578.html Any progress on it? Or are unit tests simply impossible for now? -- Phlip http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!

Hi, I am trying to generate a PDF from within a worker using PDF::Writer. In my controller I use render_to_string to create the pdf file however from what I understand render_to_string can only be used from a controller. Does anybody have any suggestions how I might be able to replicate this functionality in a worker? -- thanks, Felix -------------- next part -------------- An HTML attachment

Hemant We''ve continued testing our application with backgroundrb and found a couple of other problems when transfering large amounts of data. Both of these problems are still present in the github version of code. The first problem is an exception in the Marshal.load call in the receive_data method in the Packet::MetaPimp class. The root cause is in the BinParser module, in the arm of

I''m getting the following error (when doing script/backgroundrb start) on my local machine, which is running os x 10.4.11. However, it works just fine on my linux server. RAILS_ROOT/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:64:in `dump_object'': undefined method `write_nonblock'' for #<UNIXSocket: 0x135b5f4> (NoMethodError) I just grabbed the

Hi Erza, I am using login engine in my code...and i get the error "uninitialized constant LoginEngine and uninitialized constant LoginEngine", when i try to do a find in the worker code!!! Why am i getting this error? -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Folks, I am glad to announce 1.0 release of BackgrounDRb. This would be a major release since 0.2 release of BackgrounDRb. Here is a brief summary of changes: - BackgrounDRb is DRb no longer. It makes use of EventDriven network programming library packet ( http://packet.googlecode.com ). - Since we moved to packet, many nasty thread issues, result hash corruption issues are totally