On Tue, Jan 08, 2008 at 08:53:49PM -0600, Dustin Puryear wrote: > So, we have an internal debate at Puryear IT about how to best setup > cronjobs. First, let's assume Linux here. Every UNIX flavor has some > unique trick it likes to use, but Linux is a good example of several > ways to do cronjobs. >... > The problem I have with /etc/cron.d/ is that most people DON'T USE IT. > Sure, system scripts that come with the distro often do, but, really, > how many sysadmins create their cronjobs there? Not many in my > experience. Yet, there is a certain cleanness to /etc/cron.d/. :) > > /etc/crontab has the unique benefit of letting centralize your cronjobs, > but then you have a single file that everyone has to muck with. Yuck. > Oh, and trouble.. > > So, what are your thoughts? How do you handle this? While crontabs are handy and convenient, for anything involving system administration, I have a very strong bias in favor of techniques that are amenable to tracking changes via easily-accessed methods -- for example, by using RCS or CVS. (Caveat: I do the vast bulk of my work in FreeBSD environments, where each of RCS and CVS is part of the base system, so there is very little effort in ensuring that they are available.) Mind, there's the issue of persuading folks to actually *use* the mechanism, and to provide useful commit messages.... And although I have no personal experience with it (yet), I understand that (e.g.) cfengine can make rather constructive use of files stored in a repository (such as one maintained via CVS). Peace, david -- David H. Wolfskill david@xxxxxxxxxxxxxx I submit that "conspiracy" would be an appropriate collective noun for cats. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
Attachment:
pgpQTlyubs0qi.pgp
Description: PGP signature