From owner-freebsd-questions@FreeBSD.ORG Tue Aug 20 11:50:30 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7CCC6CF4 for ; Tue, 20 Aug 2013 11:50:30 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 435812886 for ; Tue, 20 Aug 2013 11:50:29 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r7KBoRa7089642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Aug 2013 12:50:28 +0100 (BST) Date: Tue, 20 Aug 2013 12:50:29 +0100 From: Karl Pielorz To: Arthur Chance Subject: Re: jail.conf ignoring exec.fib? Message-ID: In-Reply-To: <52131A55.2040400@qeng-ho.org> References: <98486B2D79D00F0898B7C9E6@Mail-PC.tdx.co.uk> <520B7F0F.7020006@a1poweruser.com> <1960A5B02323B4982B4C0320@Mail-PC.tdx.co.uk> <520FA592.7010305@qeng-ho.org> <52131A55.2040400@qeng-ho.org> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2013 11:50:30 -0000 --On 20 August 2013 08:27 +0100 Arthur Chance wrote: > In the source the exec.fib parameter is given as an integer, so the > quotes probably shouldn't be there, but I'm not sure whether it matters. I tried it just as 'exec.fib = 1;' originally, and it makes no difference :( > There's definitely a setfib call in the source that's done if exec.fib > exists. All I can think of right now is that you try firing up the jail > using the -v verbose flag. This should show everything the jail command > does as the jail is created. Ok, I tried that and got: " root# jail -v -c jail jail: run command: /sbin/mount -t devfs -oruleset=4 . /usr2/jails/jail/dev jail: jail_set(JAIL_CREATE) persist name=jail devfs_ruleset=4 jid=100 path=/usr2/jails/jail host.hostname=jail.somedomain.com ip4.addr=192.186.0.20 allow.raw_sockets jail: created jail: run command in jail: /bin/sh /etc/rc Setting hostname: jail.somedomain.com ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files. ln: /dev/log: Operation not permitted Starting syslogd. Clearing /tmp (X related). Updating motd:. Starting cron. Tue Aug 20 11:39:20 UTC 2013 jail: jail_set(JAIL_UPDATE) jid=100 nopersist " Certainly more detail, but no mention of fib's :( - I tried it both with, and without quotes around the FIB value. You can also see I have raw sockets available for debugging. -Karl