From owner-freebsd-rc@FreeBSD.ORG Sat Oct 29 07:18:36 2005 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81C1216A41F for ; Sat, 29 Oct 2005 07:18:36 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD23643D4C for ; Sat, 29 Oct 2005 07:18:35 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 78291 invoked by uid 0); 29 Oct 2005 07:17:53 -0000 Received: from erdgeist.org (erdgeist@erdgeist.org@80.237.196.15) by elektropost.org with AES256-SHA encrypted SMTP; 29 Oct 2005 07:17:53 -0000 Date: Sat, 29 Oct 2005 09:17:51 +0200 (CEST) From: Dirk Engling To: Yar Tikhiy In-Reply-To: <20051026051029.GA32620@comp.chem.msu.su> Message-ID: <20051029090008.J74189@erdgeist.org> References: <20051026051029.GA32620@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-rc@freebsd.org Subject: Re: A fix for `restart' X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2005 07:18:36 -0000 On Wed, 26 Oct 2005, Yar Tikhiy wrote: > Would you mind testing the following patch to /etc/rc.subr > that should remedy problems with `restart', e.g., as found > for /etc/rc.d/jail? It is safe as it doesn't affect other > commans and hence it won't disrupt your boot sequence :-) > I'm just concerned about possible side-effects for restart > I might have overlooked. The test case of scripts taking > additional arguments besides the command is the most intriguing. I included that patch and successfully ran it for a week and dozends of restarts. For me it looks like the patch solves the problem I had and stands little chance of making things worse than before. Thanks a lot. Is there any chance that this bug fix will find its way into 6.0RELEASE? Regards, Dirk