Effectively managing crontab
        Posted  
        
            by 
                jakenoble
            
        on Server Fault
        
        See other posts from Server Fault
        
            or by jakenoble
        
        
        
        Published on 2012-11-07T21:54:15Z
        Indexed on 
            2012/11/08
            5:05 UTC
        
        
        Read the original article
        Hit count: 215
        
cron
My crontab looks something like this;
1 * * * * /var/www/cron/site1.sh > /dev/null 2>&1
0 * * * * /var/www/cron/site2.sh > /dev/null 2>&1
3 * * * * /var/www/cron/site3.sh > /dev/null 2>&1
This works great and lets me place all the nasty little script calls into one place, rather than making crontab harder to read than it already is.
But, this fails massively when site2.sh needs one script to run once a day, another to run once a week and another to run every 5 minutes. And of course it gets worse as new scripts get added with different timings.
Is there a better way?
EDIT
By better I mean making it more manageable, having a large crontab is not manageable, but neither is having scripts all over the place.
Not a GUI necessarily.
© Server Fault or respective owner