I spent more than 5 hours, today, trying to make a cron job on my company web server. So, after numerous tries, I was almost ready to give up, but finally I found that even the manual say that you should not restart the crond daemon after you add a new cronjob in the crontab, because the crond daemon check every minute for changes in the crontab file and if there are any changes it run the new added cron jobs. This entry in the manual is not always true. So if you have made a cron job and in the /var/log/cron file you don’t see an entry at the time when your job was scheduled, and assuming that you are running a valid Unix command like ‘ls’, try to restart your crond daemon ( /etc/init.d/crond restart ) after adding a new cron job.
I made yesterday some tests on a Java server running on a linux machine. So I had to run the Java server and a policy server in background, then I had to stop them to change some things and then I then I started them again several times ( I will explain in my next article why I needed a policy server ) . Of course, after I repeated this operation many times, I got bored and I decided to simplify my work by creating a shell script and after some googling I found a way to run multiple background processes from a shell script.