The -RT switch starts a separate watchdog process which contains
a countdown timer.
If eValid finishes normally the last thing it does is kill the watchdog
timer started with the -RT switch.
But if the watchdog timer ends, what IT does it kill the parent
eValid process.
((This has been around a long time and I don't know if the expired
watchdog ALSO kills the other eValids or not...)).
The culprit is launching eValid from PERL...but I'm mystified
at what could be in the PERL system call that is different in
the scheduler.
But, also, the scheduler has its OWN maximum time value for a run,
and we generally use that also...
Here is a brief description of available methods for isolating
eValid playbacks in monitoring mode:
http://www.e-valid.com/Products/Documentation.9/Monitoring/guarding.playback.htmlWhy does eValid hang in the first place? Most of the time it is in the
state of trying to download a file, and the server is refusing to send
all the parts...so eValid, being a faithful robot, waits, and waits...
______________________
eValid Support Team