From owner-freebsd-jail@FreeBSD.ORG Thu Aug 6 16:36:13 2009 Return-Path: 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 C4DB7106564A for ; Thu, 6 Aug 2009 16:36:13 +0000 (UTC) (envelope-from stef-list@memberwebs.com) Received: from mx.npubs.com (mail.npubs.com [94.75.203.100]) by mx1.freebsd.org (Postfix) with ESMTP id 8CB538FC19 for ; Thu, 6 Aug 2009 16:36:13 +0000 (UTC) Received: from mx.npubs.com (avhost [94.75.203.103]) by mx.npubs.com (Postfix) with ESMTP id B1384303982E; Thu, 6 Aug 2009 16:11:18 +0000 (UTC) Received: from sqlserver1 (unknown [74.82.45.12]) by mx.npubs.com (Postfix) with ESMTP id 90CA23039807; Thu, 6 Aug 2009 16:11:17 +0000 (UTC) From: Stef Walter User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: Michael Scheidell References: <4A7AE4D4.2090600@secnap.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20090806161117.90CA23039807@mx.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Thu, 6 Aug 2009 16:11:18 +0000 (UTC) Cc: freebsd-jail@FreeBSD.org Subject: Re: crontab hanging won't die on SIGTERM in jail X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stef@memberwebs.com List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2009 16:36:14 -0000 Michael Scheidell wrote: > anyone having problems during an in jail shutdown with crontab hanging? > I have seen this in 6.4 and 7.1, on i386 and amd64. > I don't remember problems with 6.3 I see this same problem in certain jails. A jail that has this problem does it consistently, jails without the problem (on the same machine, same FreeBSD userland/kernel) don't have the problem consistently. In these cases, sending cron the TERM signal just doesn't do anything. You have to wait for at least one minute after jail startup for cron to get into this unTERMable state. I haven't had time to do further debugging on this, but I figured I'd pitch in with what I've experienced. Cheers, Stef