On Monday, Sep 9, 2002, at 16:56 US/Pacific, HENRY,MARK
(HP-Roseville,ex1) wrote:
[..]
> Also, I've had variable success with the windows task scheduler to run
> scripts frequently - has anyone any experience with using the
> scheduler vs.
> a long sleep period loop type situation and vice versa?
[..]
the 'traditional' trick that would be used on the unix side would be
something along the line of
a) a lock file
if it exists, then it has the process id of the daemon
that created it - if that process id does not correlate
to a running process of 'our name'- then this is a marooned
lock file.... put our process id in it, and move on....
b) check the process table for the existence of any processed
with our name.... we know whom we are because we can spot
our own process ID .... hence if there is another process
in the proc table - deal with it.
These are problems that arise when folks want to run cron/scheduler
based jobs - rather than working out a way to create a 'long sleep
period loop type situation' - which on the unix side would be known
as a daemon....
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
