Path: csiph.com!usenet.pasdenom.info!aioe.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Robert Klemme <shortcutter@googlemail.com>
Newsgroups: comp.lang.ruby
Subject: Re: Exit from Dir.chroot()
Date: Sat, 29 Mar 2014 16:10:53 +0100
Lines: 9
Message-ID: <bpo63uF80duU1@mid.individual.net>
References: <5ca93836-5480-494d-bcb2-21cd1204b8fc@googlegroups.com> <726c6ffa-adab-4de7-9708-07bb59c6e7ec@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net FooNDK4ub85xrjb8tfVANAhttPdeV7jjRM//oFbDlpz/LDxh4=
Cancel-Lock: sha1:NBpi1TSkeQQhkL2X0vISXoTdh8M=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
In-Reply-To: <726c6ffa-adab-4de7-9708-07bb59c6e7ec@googlegroups.com>
Xref: csiph.com comp.lang.ruby:6947

On 29.03.2014 10:22, hgarg.india@gmail.com wrote:
> Any other clear strategy, as I am using ruby in CHEF so, calling Process.exit exits the chef also.
>

Strategy should be obvious: fork, then in child: chroot, do work, exit.

Cheers

	robert