From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 21 18:17:58 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CFC9E170804; Wed, 21 Feb 2007 18:17:58 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id 588E013C46B; Wed, 21 Feb 2007 18:17:58 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id l1LI0a06070958; Wed, 21 Feb 2007 21:00:36 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Wed, 21 Feb 2007 21:00:35 +0300 (MSK) From: Maxim Konovalov To: LI Xin In-Reply-To: <45DC7F94.7010104@delphij.net> Message-ID: <20070221205826.D79626@mp2.macomnet.net> References: <20070221171816.GB2202@genius.tao.org.uk> <45DC7F94.7010104@delphij.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Josef Karthauser , hackers@freebsd.org, current@freebsd.org Subject: Re: Zombie Jails - why don't they disappear? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2007 18:17:58 -0000 On Thu, 22 Feb 2007, 01:21+0800, LI Xin wrote: > Josef Karthauser wrote: > > I've got zombie jails on a freebsd 6.x box (currently 6.2). > > There are no processes running under any of them, but they still appear > > on the jail list: > > > > server# jls > > JID IP Address Hostname Path > > 2 xxx.xxx.1.234 host1.domain /data/jails/host1 > > 1 xxx.xxx.1.235 host2.domain /data/jails/host2 > > > > I'm flumoxed as to why they're still there. There aren't any processes > > running in them: > > > > server# ps -auxww | grep J > > > > Any ideas why they are still hanging around in the jail list? > > Sockets (stuck in a state which can not be released immediately?) or > other resources? I really think that this is a bug, though. It was discussed millon times already and there is at least one open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89528 -- Maxim Konovalov