From owner-freebsd-bugs@FreeBSD.ORG Wed Jun 23 16:36:15 2010 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8993D106566B for ; Wed, 23 Jun 2010 16:36:15 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from gritton.org (gritton.org [208.92.232.93]) by mx1.freebsd.org (Postfix) with ESMTP id 52D6A8FC0C for ; Wed, 23 Jun 2010 16:36:15 +0000 (UTC) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by gritton.org (8.14.3/8.14.3) with ESMTP id o5NGFqqW011676; Wed, 23 Jun 2010 10:15:53 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <4C2232A7.2010201@FreeBSD.org> Date: Wed, 23 Jun 2010 10:13:27 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.5) Gecko/20100103 Thunderbird/3.0 MIME-Version: 1.0 To: Alexander Pyhalov References: <4C20C76C.2070005@rsu.ru> In-Reply-To: <4C20C76C.2070005@rsu.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@FreeBSD.org Subject: Re: question about /etc/rc.d/jail X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 16:36:15 -0000 There's a lot that the current jail(8) can do that /etc/rc.d/jail isn't prepared to handle. Rather than fix up the rc script, I'm working on a new jail(8) that includes a full configuration file. In the meantime, the only why to take full advantage of jail configuration is to work outside the rc framework. - Jamie On 06/22/10 08:23, Alexander Pyhalov wrote: > I currently use FreeBSD 8-CURRENT (however, not very recent). We saw > that jail naming was added to jexec call. However, /etc/rc.d/jail > doesn't set jail name on jail startup, and so something like > jexec myjailname /bin/tcsh > doesn't work. Whas it done intentionally? > The attached patch solves this problem for me...