similar to: Redirect STDOUT?

guestfish --listen necessarily redirects its stdout to /dev/null so as not to interfere with eval. The remote protocol doesn't contain any other provision for collecting stdout for the caller, so executing guestfish --remote will never generate any output. This patch fixes that by forwarding the caller's STDOUT to the listener over the unix socket connection. The listener redirects its

Hi, I get the following error from my client program when I try to call delete after my worker is completed: goten at goten-server:~/projects/svn_working/m29svn_back/app$ ruby backup_app.rb {:done=>true, :txt=>["piping to tmp", "piping done", "getting youngest", "youngest got", "destfile

I just had an interesting issue on a production system that has been running nicely for about a year. There were approximately 10,000 backgroundrb temp files in the /tmp directory. It looks like backgroundrb wasn''t cleaning them up. I noticed it with the following error: DRb::DRbConnError: drbunix:///tmp/backgroundrb.20015/ backgroundrb_logger_0_0.101544829808665 -

Hi all, I''m trying to replace an OpenWFEru/daemons-based infrastructure, with the goal being to be able to communicate with the workers to a) monitor current state and to b) initiate new actions. The short version on why these are daemons and not transient workers (that start up and shut down when they''re done with a particular task) is because they''re subscribing to

I just installed BackgrounDRb the other day. It''s working great but after I deployed to production, I noticed a couple of strange things happening: 1) I have the following code in a lib module and after deploying, IS_PRODUCTION was set to false. I''m not sure why this started occurring and the only major change was the installation of BackgrounDRb and its dependencies. Could

VDDK plugin + --run was broken because of the following sequence of events: (1) After .config_complete, server redirects stdin/stdout to /dev/null. (2) Server then calls vddk_get_ready which reexecs. (3) We restart the server from the top, but with stdin/stdout redirected to /dev/null. So saved_stdin/saved_stdout save /dev/null. (4) run_command is called which "restores"

I''m having a strange issue. The following error is printed to the backgroundrb_server.log file: failed to find slave socket </tmp/backgroundrb.803/ verification_email_delivery_worker_fafbd1e29be8b802aef4a4ffc1a35754_0_0. 126366358217085> - (RuntimeError) 20070124-17:41:29 (805) /usr/local/lib/ruby/gems/1.8/gems/slave-1.2.0/ lib/slave.rb:462:in `initialize''

Greetings, I am seeing the following in my log quite a bit 20 + times per day. The stack-trace seems tin indicate an internal issue - is concurrency related? == 0.2.1 (Released November 28, 2006 - r162) My workers continue to function; on the next iteration I believe. Any thoughts are appreciated. cheers, Jodi allow_concurrency=true Scheduler.run failure: undefined method

According to the manual, the `stdout` argument of the `system2` function can redirect output to a file. This seems to work on unix, however I can't get it to work on windows. The toy example below, no `out.txt` or `err.txt` files are created. I tried sending it to an existing file, or expand the full file path, but with no success: setwd(tempdir()) system2("whoami",

I''m having trouble getting backgroundrb up and running in a production environment. Here''s my backgroundrb.yml: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: XXX.XX.XXX.50 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 XXX.XX.XXX.51 order: deny,allow I start BackgroundRB from XXX.XX.XXX.50 with

Hi! As you might remember I''m having a problem of backgroundrb stopping calling my workers after some period of time. I tried adding logging to backgroundrb source code but it didn''t help. So, after digging through internet I''ve found several gdb tools and here''s what I''ve discovered: After attaching to a backgroundrb ruby process it turns out that it

(Sorry my last email had the wrong subject) Hi, I''ve just installed background rb 0.2.1. When I try start a worker in my application controller I receive the following error: wrong number of arguments (2 for 1) - (ArgumentError) /home/chris/projects/call_manager/trunk/call_manager_app/vendor/plugins/backgroundrb/server/lib/backgroundrb/middleman.rb:211:in `initialize''

Hello, There appears to be an error in the stderr redirection of the crontab rsync entry. In Bourne shell and compatibles (crontab entries are run by the Bourne shell) redirections are processed from left to right and "2>&1" redirects the stderr to the same location stdout is currently directed and not to stdout. Hence: cmd 2>&1 > log directs stderr to the

Hello all, We''re currently running version .1.x in our environment. We would like to move to .2.x to take advantage of some of the improvements made running in a multi-process environment. We deploy to a linux environment but develop locally in Windows. I''m aware that a number of people have reported the ability to run .2.x of backgroundrb inside cygwin, and for the most part,

for some strange reason this error occours when i create one worker from another BUT only when i derive worker class from Worker::Base instead or Worker::RailsBase - when change it back it works fine, child worker can have empty do_work, but this error still ocours Bad file descriptor (Errno::EBADF) /var/lib/gems/1.8/gems/slave-1.2.0/lib/slave.rb:214:in `for_fd''

Hello everyone, I''m stuck with this very obscure error whenever I try to create a new worker. My worker is a subclass of BackgrounDRb::Worker::RailsBase, and if you follow the stack trace below, you can tell that the error occurs while trying to load Rails. There is no problem starting up the server, by the way. Does anyone have any idea what might be causing this? I didn''t have

Hey, I have scheduled script that is not working very well. It will only run once or twice before I have to restart the server to get it running again. If I try to the worker manually after it has stopped exceuting the schedule I get this in the server log: 20070522-07:33:36 (5030) Connection reset by peer - (DRb::DRbConnError) 20070522-07:33:36 (5030) /usr/local/lib/ruby/1.8/drb/drb.rb:566:in

Hello - Can anyone explain why I get the stack trace in background_server.log when I try to start my first worker? I don''t get this on subsequent workers, only the first one. I should note, the method I am using to start backgroundrb is documented in the archives, and is likely the root of this problem. Suggestions about how to "fix" or avoid this issue are appreciated.

Hi, I have an application that receives XML files, and then hands each one off to a backgroundrb worker to parse and store the info. Everything was working, until I needed to support a larger character set. So I added the following to the top of my XML files: <?xml version="1.0" encoding="ISO-8859-1"?> Adding this worked fine when I tested it without using

I''m struggling to keep backgroundrb v2 running for more than 24 hours. It appears to be running fine for a while, then tries to fire off a worker (exactly the same worker it''s been running for the past few hours), and it suddenly dies. I haven''t found any pattern for the cause of this. In backgroundrb_server.log, the final entry is this : 20070206-10:41:45