From owner-freebsd-jail@FreeBSD.ORG Fri Aug 7 01:11:18 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 E3DBF106564A for ; Fri, 7 Aug 2009 01:11:18 +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 ABCD08FC17 for ; Fri, 7 Aug 2009 01:11:18 +0000 (UTC) Received: from mx.npubs.com (avhost [94.75.203.103]) by mx.npubs.com (Postfix) with ESMTP id 774E8303974A; Fri, 7 Aug 2009 01:11:17 +0000 (UTC) Received: from sqlserver1 (unknown [74.82.45.12]) by mx.npubs.com (Postfix) with ESMTP id 5A7D53039712; Fri, 7 Aug 2009 01:11:16 +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> <20090806161117.90CA23039807@mx.npubs.com> <4A7B103F.6040400@secnap.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20090807011116.5A7D53039712@mx.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Fri, 7 Aug 2009 01:11:17 +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: Fri, 07 Aug 2009 01:11:19 -0000 Michael Scheidell wrote: > you arn't running ezjail, are you? could there be anything in ezjail > that would do this? I'm not running ezjail, and I don't think it's related. For me the common denominator for the jails that exhibit this, is that java (java/jdk15) is started from an rc.d script. This is anecdotal at best. It also doesn't happen immediately. Today I was playing with such a jail and cron would happily restart (ie: '/etc/rc.d/cron restart') until I left it alone for a few hours. I have a dummy cron job (eg: /usr/bin/true), which runs every minute. /var/log/cron shows that the job is still being run even when cron is ignoring the TERM signal. Cheers, Stef