Date: Tue, 4 Nov 1997 13:46:14 -0500 (EST) From: spork <spork@super-g.com> To: Mike Smith <mike@smith.net.au> Cc: Brandon Gillespie <brandon@roguetrader.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/*.conf file for daily/weekly/security etc maintenance Message-ID: <Pine.BSF.3.96.971104134344.11919A-100000@super-g.inch.com> In-Reply-To: <199711040448.PAA01232@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm not sure if you folks have seen this, but NetBSD has something like this for daily/weekly/monthly: # $NetBSD: daily.conf,v 1.2 1997/01/20 06:08:36 mycroft Exp $ # # see daily.conf(5) for more information. find_core=NO expire_news=NO purge_accounting=YES run_msgs=NO run_calendar=NO check_uucp=NO check_disks=YES check_mailq=NO check_network=YES run_fsck=NO run_rdist=NO run_security=YES It shouldn't matter too much where you put it, just so everything is all in one place... IMO, the NetBSD way is a bit messy as it adds three more files to an already-crowded /etc. Charles On Tue, 4 Nov 1997, Mike Smith wrote: > > > > > > 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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971104134344.11919A-100000>