Date: Mon, 25 Sep 1995 11:17:52 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: gryphon@healer.com (Coranth Gryphon) Cc: jmb@kryten.atinc.com, terry@lambert.org, hackers@FreeBSD.ORG, peter@taronga.com Subject: Re: ports startup scripts Message-ID: <199509251817.LAA05510@phaeton.artisoft.com> In-Reply-To: <199509251441.KAA12169@healer.com> from "Coranth Gryphon" at Sep 25, 95 10:41:35 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > It may also need to add a cron job to rotate the damons logs. > > No. With the new "daily" script handler (Jordan, have you told anyone > else about this yet?) all it needs to do is add a line to the scheduled > jobs config file (current name "sched.conf" like: > > rotate_log daily /some/log/file What if I want to rotate them twice a week instead of daily? What about twice a day? > > Ordering guarantees within a single run level/state are hard to provide > > with the single monolithic file model. > > Actually, a single file is the easiest to control ordering in. > Last I checked, line 1 always came before line 2. :-) The problem is that the line starts are not a fixed locations and are therefore variant without whole file locking. Which is bad. > > Finally, what if I don't want to delete the package, I just want to > > disable it? How to I prevent the package daemon's and cron jobs from > > Comment out the line in the control file? OK. Then: 1) How do I tell which line(s) correspond to which package? 2) How do I reenable it? 3) How do I do this from an administrative utility instead of having to actually know what's what myself? > > Typically, I'd put the "cron" jobs as at commands in the startup script, > > though this begs the question of providing configurability under > > administrative control (for instance, what if I want to specify a higher > > or lower frequency of log rotation?). Cron actually faces the same > > issues as init. > > As above, given that you have the granularity of "daily", "weekly", or > "monthly". I suppose we could always add "bi-weekly" and "bi-monthy" :-/ The question was in terms of specification by administrative fiat after boot time. With a cron job, I can change the file and reset cron. With an at job, I am pretty much screwed. The cron data files suffer from the same failings as the mondo-data-file correspondance ambiguities: how do I correlate lines with administrative actions on a package basis? The problem is that the n:m mapping goes to hell rather quickly when it becomes n:m:l mapping. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509251817.LAA05510>