[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: conf/119995: [patch] New rc.d script ddb to load ddb scripts from /etc/ddb.conf
- To: Brooks Davis <brooks_(_at_)_freebsd_(_dot_)_org>
- Subject: Re: conf/119995: [patch] New rc.d script ddb to load ddb scripts from /etc/ddb.conf
- From: Robert Watson <rwatson_(_at_)_FreeBSD_(_dot_)_org>
- Date: Sat, 26 Jan 2008 22:41:13 +0000 (GMT)
- Cc: freebsd-bugs_(_at_)_freebsd_(_dot_)_org, Doug Barton <dougb_(_at_)_freebsd_(_dot_)_org>, freebsd-rc_(_at_)_freebsd_(_dot_)_org, bug-followup_(_at_)_FreeBSD_(_dot_)_org
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
University of Cambridge
freebsd-bugs_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org