From owner-svn-src-all@FreeBSD.ORG Mon Oct 14 18:52:34 2013 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4487EDB; Mon, 14 Oct 2013 18:52:34 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4EB062EC1; Mon, 14 Oct 2013 18:52:34 +0000 (UTC) Received: from alph.d.allbsd.org (p4181-ipbf1307funabasi.chiba.ocn.ne.jp [123.225.173.181]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r9EIqGXI016517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Oct 2013 03:52:26 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.7/8.14.5) with ESMTP id r9EIqE0A019469; Tue, 15 Oct 2013 03:52:15 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Tue, 15 Oct 2013 03:52:12 +0900 (JST) Message-Id: <20131015.035212.830333497899935494.hrs@allbsd.org> To: gavin@FreeBSD.org Subject: Re: svn commit: r256256 - in head: . etc etc/defaults etc/rc.d share/man/man5 usr.sbin/jail From: Hiroki Sato In-Reply-To: References: <04E9979E-1D97-4AA2-A7AE-F9D8457B3599@FreeBSD.org> <20131012.015639.236155929172394900.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Tue_Oct_15_03_52_12_2013_805)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Tue, 15 Oct 2013 03:52:26 +0900 (JST) X-Spam-Status: No, score=-99.0 required=13.0 tests=CONTENT_TYPE_PRESENT, SPF_SOFTFAIL,USER_IN_WHITELIST,X_CHINESE_RELAY autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: svn-src-head@FreeBSD.org, remko@FreeBSD.org, src-committers@FreeBSD.org, svn-src-all@FreeBSD.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Oct 2013 18:52:34 -0000 ----Security_Multipart(Tue_Oct_15_03_52_12_2013_805)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Gavin Atkinson wrote in : ga> > re> I was not expecting this much fallout from this change, others that ga> > re> will be upgrading will loose the ability to start their jails until ga> > re> they can ga> > re> resolve this by hand. ga> > ga> > Can you send me your ezjail configuration and differences of the ga> > results (error messages, mount handling, etc) between old and new ga> > rc.d/jail? ga> ga> The issue for me is that the /var/run/jail_${jailname}.id files are no ga> longer created, which ezzjail uses to keep track of jail state. ga> ga> As a temporary workaround, for each jail I have on the host done ga> echo $jail_id > /var/run/jail_${jailname}.id ga> and this allows me to manage that jail again from within ezjail. Thank you for your report. I noticed this broke "ezjail-admin console" and so on. I am working on fixing it now... -- Hiroki ----Security_Multipart(Tue_Oct_15_03_52_12_2013_805)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlJcPVwACgkQTyzT2CeTzy0jzQCggwJ7I8tvmTHQMR6xW2Wp5Peh x/UAnjqFOUcdCAurmUzMiodvBFHb0OgK =w5/v -----END PGP SIGNATURE----- ----Security_Multipart(Tue_Oct_15_03_52_12_2013_805)----