From: ara.t.howard@...
Date: 2007-04-30T07:05:24+09:00
Subject: Re: Strange DRb and fork issues

On Mon, 30 Apr 2007, Farrel Lifson wrote:

> On 29/04/07, Ezra Zygmuntowicz <ezmobius@gmail.com> wrote:
>> I'll save you a lot of hassle. Go grab the slave gem off rubyforge.
>> It does exactly what you are trying to do. It allows you to fork
>> child objects and it sets up a drb connection and a heartneat between
>> the child and parent so if the parent dies, the children will also die.
>
> Thanks, I'll check it out, although I would really like to work out what the
> problem is with my code. I'll look through the source of Slave and see if I
> can find some hints.
>

i reccomend trying to using slave.rb if you can - of course, as the author,
i'm biased.  it's really tricky connecting parent/child drb processes: the key
is that you cannot carry the drb objects across the fork, you must setup each
new drb object in the child and arrange for the parent to find it.  this, as
ezra mentions, exactly what slave does.  if you have examle code we can
suggest how to plug slave into it.

regards.

-a
-- 
be kind whenever possible... it is always possible.
- the dalai lama