From owner-freebsd-arch@FreeBSD.ORG Sun Aug 4 17:15:52 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 58A70175 for ; Sun, 4 Aug 2013 17:15:52 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 373492074 for ; Sun, 4 Aug 2013 17:15:51 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r74HFlLB050322; Sun, 4 Aug 2013 17:15:47 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id ryppdiwnp2k5wgqnayac494zy2; Sun, 04 Aug 2013 17:15:47 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: Reliable process tracking Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <20130804134658.GC35080@stack.nl> Date: Sun, 4 Aug 2013 10:15:47 -0700 Content-Transfer-Encoding: 7bit Message-Id: <37E22E4B-4710-42DB-AF82-1F4AF26D6005@kientzle.com> References: <20130804134658.GC35080@stack.nl> To: Jilles Tjoelker X-Mailer: Apple Mail (2.1283) Cc: freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2013 17:15:52 -0000 On Aug 4, 2013, at 6:46 AM, Jilles Tjoelker wrote: > When shutting down a service or requesting status, rc.subr currently > uses a combination of pidfiles and process names. This is fairly but not > completely reliable once it is set up correctly (which can take a lot of > work and possibly patching the daemon to use pidfile(3) from our > libutil). It is also incapable of killing multiprocess daemons such as > CGI web servers without cooperation of the daemon. > > I think what is needed here is a facility that marks a process and all > of its descendants. It sounds like all you really need is some way to signal a process and all descendants. Why do you need to actively mark and/or track them? Tim