On Wednesday 27 September 2006 19:08, Claes at work wrote:
It can be done, though: have your cron job install a separate crontab file, replacing the existing one. At the end of your job (or at the beginning), do:
crontab my_new_crontab_file
Interesting idea.. but a little strange too. At least for this purpose, when I want to schedule one shot jobs. Your suggestion is to have one crontab file for each job and "chain them"?
i wouldn't try it, no - too many potential problems and a pain in the butt to debug. But it might be a solution to what you're trying to do. A lock-file mechanism would be more practical and less error-prone, i think. Or, of course, what you suggested:
I will write a python script with a scheduling queue and timers. I think that will work better for me.
-- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts