> > > The file /etc/init.d is a joke. All that to create a lock file for a > > program it does not run, That is at least a minor violation of the > > concept behind the scripts in /etc/init.d > > If you have a better way to enable/disable automatic running of a cron > job that is both simpler and fits your idea of what should be, then > please let us all hear from the expert. > With out reacting to the sarcasm yeah there are better ways. Look at the way slocate.cron does it. init.d scripts are to start and stop daemons not to create lock files. After all, the arguments for these scripts are start and stop. Second, one of the convention behind both Linux and Unix is the existence of a lock file means its associated daemon is running. To have a lock file exist when the daemon is not running violates this convention -- ======================================================================= Humans do claim a great deal for that particular emotion (love). -- Spock, "The Lights of Zetar", stardate 5725.6 ------------------------------------------- Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484
