I ran into a problem with my cronjobs overlapping. I set each cronjob to every five minutes in order to fit them all in but they started to fall behind and causing a massive build up on the server.
So i made a quick script that pulls all the cronjob commands from a text file and runs them one by one. The next script doesn't start till the one before it finishes. This seems to be working out for me and is causing a lot less pain on the server. It also makes adding cronjobs a lot easier and I can add as many domains as I'd like without ever overloading the server. Since its always running no more than one job.
If this sounds like something all you noncoders out there might be interested in getting your hands on let me know and I'll post it up.
UpdateHere it is guys and gals.
Download Link: http://www.bluehatseo.com/tbs/tbscron.zipDescription: This in a sense is a concatinated cronjob script for TBS. you run one cronjob and it will first check to see if the script has finished from the last time it ran(checks the first line of crons.txt for a 0). If it is still in the process of running then it quietly exits. If it is complete then it begins, and starts one by one executing all the cronjobs you listed in crons.txt. This ensures that the script never overlaps itself, so you can technically have as many tbs domains as you would like, it would just automatically spread out the cronjobs to run less often. It also makes it a ton easier to add and edit your probably huge growing list of cronjobs. You can set the cronjob script to run as often as you'd like(i run once per hour).
#Instructions1-open cron.cgi and crons.txt in notepad. edit the "path to crons.txt line" with your full server path to the crons.txt. Then make sure the first line in crons.txt is 0 and then list all your cronjobs on seperate lines below it. Add as many as you'd like.
2-upload cron.cgi and crons.txt to the cgi-bin on your webserver. chmod permissions on cron.cgi to 755 and crons.txt to 777.
3-put in a cronjob that runs the cron.cgi
example:
perl /var/www/mydomain.com/www/cgi-bin/cron.cgiset the cronjob to as often as you would like(I use every hour, i wouldn't recommend any less than that).
So presumably, you would set your pings within TBS to "run pings as many times as cron would start it" after the installation of this script?