From owner-freebsd-hackers Mon Nov 3 12:32:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01120 for hackers-outgoing; Mon, 3 Nov 1997 12:32:33 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01100 for ; Mon, 3 Nov 1997 12:32:28 -0800 (PST) (envelope-from brandon@roguetrader.com) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id NAA23727 for ; Mon, 3 Nov 1997 13:32:28 -0700 (MST) Date: Mon, 3 Nov 1997 13:32:28 -0700 (MST) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: /etc/*.conf file for daily/weekly/security etc maintenance Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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). If there is interest, I could make the changes to the files which would use it, to be optional/configurable. -Brandon Gillespie