From owner-freebsd-hackers Mon Nov 3 20:34:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08221 for hackers-outgoing; Mon, 3 Nov 1997 20:34:06 -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 UAA08211 for ; Mon, 3 Nov 1997 20:33:59 -0800 (PST) (envelope-from brandon@roguetrader.com) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id VAA26639; Mon, 3 Nov 1997 21:33:57 -0700 (MST) Date: Mon, 3 Nov 1997 21:33:54 -0700 (MST) From: Brandon Gillespie To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/*.conf file for daily/weekly/security etc maintenance In-Reply-To: <199711040146.MAA00560@word.smith.net.au> 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 On Tue, 4 Nov 1997, Mike Smith wrote: > > 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. I thought about it, but is it appropriate? rc.conf is for startup things, no? regular maintenance.. *shrug*