From owner-freebsd-hackers Mon Nov 3 20:52:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA09201 for hackers-outgoing; Mon, 3 Nov 1997 20:52:43 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA09195 for ; Mon, 3 Nov 1997 20:52:37 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id PAA01232; Tue, 4 Nov 1997 15:18:45 +1030 (CST) Message-Id: <199711040448.PAA01232@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brandon Gillespie cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/*.conf file for daily/weekly/security etc maintenance In-reply-to: Your message of "Mon, 03 Nov 1997 21:33:54 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Nov 1997 15:18:45 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > Just propose your extensions to rc.conf; everything should be in there. > > I thought about it, but is it appropriate? rc.conf is for startup things, > no? regular maintenance.. *shrug* rc.conf is for general parametric information; whether it be startup or periodic. Things like the named flags etc. are consumed by the named.* scripts and so forth. Unless there's a _really_ compelling reason, rc.conf is the way to go. mike