From owner-freebsd-jail@FreeBSD.ORG Tue Nov 11 21:56:23 2014 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD9DF88D for ; Tue, 11 Nov 2014 21:56:23 +0000 (UTC) Received: from m2.gritton.org (gritton.org [63.246.134.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8618281 for ; Tue, 11 Nov 2014 21:56:23 +0000 (UTC) Received: from m2.gritton.org (gritton.org [63.246.134.121]) by m2.gritton.org (8.14.9/8.14.9) with ESMTP id sABLuExg039810; Tue, 11 Nov 2014 14:56:14 -0700 (MST) (envelope-from jamie@freebsd.org) Received: (from www@localhost) by m2.gritton.org (8.14.9/8.14.9/Submit) id sABLuDgc039809; Tue, 11 Nov 2014 14:56:13 -0700 (MST) (envelope-from jamie@freebsd.org) X-Authentication-Warning: gritton.org: www set sender to jamie@freebsd.org using -f To: freebsd-jail@freebsd.org Subject: Re: Fwd: Re[2]: fails exec.postsop after shutdown jail. X-PHP-Originating-Script: 0:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 11 Nov 2014 14:56:13 -0700 From: James Gritton In-Reply-To: References: Message-ID: <7c117eea78240220d57a9650161407f6@gritton.org> X-Sender: jamie@freebsd.org User-Agent: Roundcube Webmail/1.0.3 Cc: =?UTF-8?Q?=D0=91=D0=BE=D1=80=D0=B8=D1=81?= X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2014 21:56:24 -0000 On 2014-11-10 02:13, Борис wrote: >> Everything looks right to me. I've tried it out on my own system, and >> it worked as expected. The only difference is I don't have VIMAGE, so >> I commented out the vnet stuff (including the exec.start that goes >> along with it). >> >> So maybe the trouble is with vnet? Even still, that looks correct. >> I'm just able to test it at the moment. Regardless, vnet shouldn't >> affect the nullfs mount. >> >> What output do you get for "jail -vr testjail1"? >> >> - Jamie > I do not understand anything, after booting my test stand to see > output "jail -vr testjail1" all work's fine! > root@:~ # jail -rv testjail1 > testjail1: run command in jail: /bin/sh /etc/rc.shutdown > Stopping cron. > Waiting for PIDS: 4040. > Stopping sshd. > Waiting for PIDS: 4036. > . > Terminated > testjail1: sent SIGTERM to: 3965 > testjail1: removed > testjail1: run command: ifconfig epair0a destroy > testjail1: run command: /sbin/umount /jails/testjail1/dev > testjail1: run command: /sbin/umount -t nullfs > /jails/testjail1/usr/ports > > thank's for response, need more tests...subscribe@freebsd.org" OK, I've tried it with VIMAGE now, and with the relevant bits of the jail.conf included. It still all worked for me, creating the jail with the right IP address on epair0b, and removing both of the epairs when the jail was removed. So yeah, I guess it needs more tests - sorry I couldn't do anything to make sense of it. - Jamie