> > * You could have the init.d script create and delete the crontab > entry. Certainly not much more palatable. > > * Accept the status quo, where package installation is equated with > "I want to run the service". > > * Don't involve cron at all: start a shell script in the background, > which fires off the real job once every five minutes. > > * Make the admin put the crontab in place and ignore the standard > method of specifying what services should run altogether. > > I prefer the Yum method, myself. > The other option I've considered is simply not installing the cron job at all and requiring the user to do it. The user already has to configure db connections in /etc/cacti I might just add a step that says "copy the cron script from the cacti doc's to /etc/cron.d/" -Mike -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list