From: matz@... (Yukihiro Matsumoto)
Date: 2003-05-14T13:49:00+09:00
Subject: Re: RCR for child execution

Hi,

In message "Re: RCR for child execution"
    on 03/05/14, "Simon Strandgaard" <0bz63fz3m1qt3001@sneakemail.com> writes:

|Yes your code does *most* of what I want.. but unfortunatly not all.
|I want a permanent sandbox,  not a setup/eval/restore sandbox.
|The reason why I want a permanent sandbox:
|I have instances of Ruby classes owned by C++ which I access over long
|time. 

It's not possible without breaking UNIX process model, which Ruby
depends on.  I don't want break this.  It would screw up processes.

How about forking off the Ruby interpreter to create a sandbox.  By
this way, you can create your own Ruby sandbox?

  +---------+
  |Your C++ |
  | process | <= prepare pipes, fork, reopen fd(0,1,2), ruby_run()
  +--||-----+
  +--||-----+
  |Your Ruby| <= stdin/stdout/stderr is swapped before ruby_run()
  |  process|
  +---------+
							matz.