From owner-freebsd-hackers Mon Nov 3 17:52:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23687 for hackers-outgoing; Mon, 3 Nov 1997 17:52:53 -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 RAA23676 for ; Mon, 3 Nov 1997 17:52:48 -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 MAA00560; Tue, 4 Nov 1997 12:16:57 +1030 (CST) Message-Id: <199711040146.MAA00560@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brandon Gillespie cc: 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 13:32:28 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Nov 1997 12:16:56 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Just curious, why dont we create a .conf file in /etc like the rc.conf, > but for daily maintenance--allow people to easilly enable/disable options > without having to get in and make lots of changes to the > daily/weekly/monthly/security/whatnot files? I've been doing this sortof > thing with my own changes, where the config file is /etc/janitor.conf, > in the same format as /etc/rc.conf (but for periodic > janitorial/maintenance items). Just propose your extensions to rc.conf; everything should be in there. mike