The killtime is designed to prevent the job from being in the queue,
unsent too long. It's not designed to assist in the control of how many
attempts there should be or how much time is allowed between attempts.
Let's say that I have an important fax that needs to get sent urgently.
I increase the priority on the job and I set a killtime that is short
enough that if there's a queue problem that I'll get notification of the
killtime being exceeded soon enough that I can get the urgent fax sent
out in another way. Okay, now let's say that all of the modems are hung
or are having some kind of freak problem. Or let's say that there is a
1000-page fax in the queue that is going at 2400 bps.
In this case the killtime setting will alert me to the problems on the
server without the job ever having been tried.
Killtime is good as it is. If there is some reason to manage how much
time elapses from the moment that the job is first attempted until the
job should be killed, then we'll need a separate parameter option for
that... although I do think that can be better-controlled by other
options already available.
Lee.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
