From owner-freebsd-jail@FreeBSD.ORG  Mon Jun 14 14:02:43 2010
Return-Path: <owner-freebsd-jail@FreeBSD.ORG>
Delivered-To: freebsd-jail@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1811E106566C
	for <freebsd-jail@freebsd.org>; Mon, 14 Jun 2010 14:02:43 +0000 (UTC)
	(envelope-from jwhatley@rhyton.com)
Received: from lion.rhyton.com (mail.rhyton.com [70.85.6.241])
	by mx1.freebsd.org (Postfix) with ESMTP id C7B1C8FC17
	for <freebsd-jail@freebsd.org>; Mon, 14 Jun 2010 14:02:42 +0000 (UTC)
Received: from sephariel (azzuro.rhyton.com [70.91.115.129])
	(authenticated (0 bits))
	by lion.rhyton.com (8.12.10/8.11.6) with ESMTP id o5EDaaxb091636
	for <freebsd-jail@freebsd.org>; Mon, 14 Jun 2010 09:36:37 -0400 (EDT)
From: "Jacob Whatley" <jwhatley@rhyton.com>
To: <freebsd-jail@freebsd.org>
Date: Mon, 14 Jun 2010 09:36:40 -0400
Message-ID: <009001cb0bc6$a2641810$e72c4830$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsLxp6z6mrEjdkAQ4ebZFyXCaCSvA==
Content-Language: en-us
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: jid's not refreshing after jail shutdown
X-BeenThere: freebsd-jail@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion about FreeBSD jail\(8\)" <freebsd-jail.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-jail>,
	<mailto:freebsd-jail-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-jail>
List-Post: <mailto:freebsd-jail@freebsd.org>
List-Help: <mailto:freebsd-jail-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-jail>,
	<mailto:freebsd-jail-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2010 14:02:43 -0000

Hello group!

 

On 8.0 Release, our system is setup so that we specify the jid when a jail
is built, which we make numerical (ie, 1001, 1002, etc..). This works great
for consistency and for setup scripts. However, we are running into a
problem that after shutting down a jail (or group of jails) using 'jail -r
<jid>', when we attempt to start the jail(s) anew, we get the error:

 

jail: jail <jid indicated> already exists

 

Running jls shows no active jail for that jid. Is there something that we
can do to flush whatever buffer is holding the old jid data, so that we may
restart a dead jail with the same jid? Incidentally, this happens more often
than not, but occasionally and after a few minutes we can run 'jail -c
.....' and it will not bomb.

 

Thanks!

 

Jake Whatley, Developer

Rhyton Corporation

jwhatley@rhyton.com

http://rhyton.com

 

****************************