We don't let developers run the job .... but your idea is good about semaphore ....
Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! -----Original Message----- Sent: Friday, March 15, 2002 8:59 AM To: Multiple recipients of list ORACLE-L I also agree, cron WORKS well ! The only thing I would add to cron jobs (shell scripts) is to use a semaphore file. e..g. —--------------------------------------- semfile=/tmp/$0.RUNNING if [ -f $semfile ] ; then exit ; fi touch $semfile DO SOME SHELL STUFF rm $semfile exit —--------------------------------------- This way no matter how frequent you run the job or how long it takes the job to run, it still works. I had a developer run a job every 5 mins but the job took 15 mins to run, so you can guess what begins to happen after a few days :-) Gene
*********************************************************************2 This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you. *********************************************************************2
