From owner-freebsd-rc@FreeBSD.ORG Sat Jan 26 22:59:25 2008 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 E35FF16A417; Sat, 26 Jan 2008 22:59:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id BBA8813C468; Sat, 26 Jan 2008 22:59:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 040EC4E75F; Sat, 26 Jan 2008 17:41:14 -0500 (EST) Date: Sat, 26 Jan 2008 22:41:13 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Brooks Davis In-Reply-To: <20080126175535.GA52539@lor.one-eyed-alien.net> Message-ID: <20080126223558.J69773@fledge.watson.org> References: <200801260814.m0Q8EDeT053102@freefall.freebsd.org> <479B5D72.2010706@FreeBSD.org> <20080126175535.GA52539@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-bugs@freebsd.org, Doug Barton , freebsd-rc@freebsd.org, bug-followup@FreeBSD.org Subject: Re: conf/119995: [patch] New rc.d script ddb to load ddb scripts from /etc/ddb.conf 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, 26 Jan 2008 22:59:26 -0000 On Sat, 26 Jan 2008, Brooks Davis wrote: > IMO we want this in the base and ideally this script or the crash dump > script would grow the option to mail text dumps somewhere automatically (off > by default of course). This should be as tightly integrated as we can > reasonably make it. I think I'd like to see something along these lines in the base, as offering tools to help autonatically configure DDB scripting isn't all that different from offering tools to configure firewalls, run user scripts, etc. However, I wonder if we should consider doing it slightly differently than proposed. One of the things I like about the way we do ipfw rulesets is that we allow a filename to be specified that contains a series of commands to pass to the ipfw command-line tool, rather than a file that contains a list of rules. This means that as the ipfw tool becomes more capable, the configuration file supports those changes in a natural way. I.e., rather than having ddb.conf contain: scriptname="foo bar baz" It should perhaps instead contain: script scriptname="foo bar baz" We will need to teach ddb(8) to do this in a similar manner to ipfw(8). Robert N M Watson Computer Laboratory University of Cambridge