From owner-freebsd-rc@FreeBSD.ORG Tue Jun 8 21:45:29 2010 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 768701065670 for ; Tue, 8 Jun 2010 21:45:29 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) by mx1.freebsd.org (Postfix) with ESMTP id 3F92E8FC2C for ; Tue, 8 Jun 2010 21:45:29 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id 2A1201DD657 for ; Tue, 8 Jun 2010 23:45:27 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id 1D25417250; Tue, 8 Jun 2010 23:45:27 +0200 (CEST) Date: Tue, 8 Jun 2010 23:45:27 +0200 From: Jilles Tjoelker To: freebsd-rc@FreeBSD.org Message-ID: <20100608214526.GB9977@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: ugly output of wait_for_pids with kill(1) builtin 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: Tue, 08 Jun 2010 21:45:29 -0000 I'm experimenting with making kill an sh(1) builtin (*). However, this makes wait_for_pids's output ugly: the kill builtin is too fast and almost always detects the process is still running or a zombie, so the Waiting for PIDS message appears for all daemons. NetBSD does not appear to have this problem as much as they only have KEYWORD: shutdown where it is strictly necessary. Any ideas how to avoid this? One such option would be some sort of modification to pwait(1). (*) Reasons to do this: 1. allow kill %1 2. make sure kill is found before $PATH 3. make kill work even if fork is impossible -- Jilles Tjoelker