From owner-freebsd-questions@FreeBSD.ORG Thu Nov 28 12:58:47 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 ESMTPS id 2052BA7F for ; Thu, 28 Nov 2013 12:58:47 +0000 (UTC) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CB12B1C7E for ; Thu, 28 Nov 2013 12:58:46 +0000 (UTC) Received: from laptop3.herveybayaustralia.com.au (laptop3.herveybayaustralia.com.au [192.168.0.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id D0A3927325 for ; Thu, 28 Nov 2013 22:58:44 +1000 (EST) Message-ID: <52973E04.2020002@herveybayaustralia.com.au> Date: Thu, 28 Nov 2013 22:58:44 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130530 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: chromium inside the jail References: <65e0f759da27c85615f3190a5e48f8bb@vmeta.jp> <20131128001512.GA59354@icepick.vmeta.jp> In-Reply-To: <20131128001512.GA59354@icepick.vmeta.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2013 12:58:47 -0000 On 11/28/13 10:15, Koichiro IWAO wrote: > On Wed, Nov 27, 2013 at 03:50:34PM -0800, Adrian Chadd wrote: >> Isn't it a global setting you do in the machine root itself, not the jail? > You're right however chromium window whiteouts and nothing's drawn. This > behaviour is as same as if kern.ipc.shm_allow_removed is set to 0. I've > checked sysctl inside the jail, kern.ipc.shm_allow_removed is actually > set to 1. If it doesn't matter, what can I do next? > This setting might actually be violating jail policy (shm?) - in other words you may as well not run in the jail. Might be why it doesn't work.