RE: Monitor for existing job.

["Hall, Philip" <phall@xxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
> And how would you prevent another
> one with the same simple name but
> using completely different resources
> to run or maybe it would be ok to run
> this as there is no conflict.

This brings us back full circle to what Mike wanted, a way to ensure that if
the job was already running that a duplicate couldn't be run at the same
time.

The various answers all described that the code in the job create some kind
of semaphore/mutex/flag that is only live while the job runs - if a second
copy tries to run, it will see the 'in-use' and quit.

Lots of jobs do this kind of thing (sometimes explicitly, sometimes not), on
many OS's.

--phil