btw: warum heißt es cron-Job, wenn es zufällig ist? *g*

Weil der Erfinder vom (ursprünglichen) cron gedacht hat, es würde regelmäßig sein ...

Alexander

http://hegel.ittc.ukans.edu/topics/linux/man-pages/man1/crontab.1.html

crond automatically detects changes in the time. Reverse-indexed time changes less then an hour old will NOT re-run crontab commands already issued in the recovered period. Forward-indexed changes less then an hour into the future will issue missed commands exactly once. Changes greater then an hour into the past or future cause crond to resynchronize and not issue missed commands. No attempt will be made to issue commands lost due to a reboot, and commands are not reissued if the previously issued command is still running. For example, if you have a crontab command 'sleep 70' that you wish to run once a minute, cron will only be able to issue the command once every two minutes. If you do not like this feature, you can run your commands in the background with an '&'.