From owner-freebsd-rc@FreeBSD.ORG Mon Jul 1 13:25:43 2013 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1B8966F2; Mon, 1 Jul 2013 13:25:43 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id D30BF1BD0; Mon, 1 Jul 2013 13:25:42 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r61DPf88030031; Mon, 1 Jul 2013 07:25:41 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r61DPfSX030028; Mon, 1 Jul 2013 07:25:41 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 1 Jul 2013 07:25:41 -0600 (MDT) From: Warren Block To: Jilles Tjoelker Subject: Re: Proposal: multi-instance and self-contained rc.d script In-Reply-To: <20130630221032.GB43309@stack.nl> Message-ID: References: <20130701.062953.1443190655468739608.hrs@allbsd.org> <20130630221032.GB43309@stack.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 01 Jul 2013 07:25:41 -0600 (MDT) Cc: freebsd-rc@FreeBSD.org X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 01 Jul 2013 13:25:43 -0000 On Mon, 1 Jul 2013, Jilles Tjoelker wrote: > On Mon, Jul 01, 2013 at 06:29:53AM +0900, Hiroki Sato wrote: ... >> b) Make rc.d/foo always have rc.d/foo(8) manual page. > > However, I don't like another set of manual pages. They could be autogenerated by reading comments and variable values in the rc.d scripts. Of course the rc.d scripts would have to contain that information. At least it would be in the same file, helping to keep the doc in sync with the script. This is not to suggest a full man page in the script, just a short text summary along with variables that may be used. '/etc/rc.d/routed manpage' would return the generated mdoc code. '/etc/rc.d/routed help' could pipe that output to man. What filenames or section would be used for the generated man pages? routed(8) already exists, and "rc.d/routed.8" has problems both as a filename and an argument to man(1).