![]() |
In your previous post you stated that the jobs would be re-submitted with a 'jitter', I assume that this "jitter" occurs because it is from the "current time" and the re-schedule time is added in to that ., as aposed to the resubmittal being "TTS"+ re-schedule time.
what would be the effect of taking the old "TTS"+ the reschedule time , and using that as the resubmit fire time?
I would guess that this will put the jobs back into the re-try queue so they all fire at the same time ( if they were origionally all sent with the same TTS), that might negate the need to play about with an admin agent, or is that likely to messup other users?
we might need a bit of logic to check that the "old TTS+reschedule time" was not less that the current time, just incase it was running on a heavily loaded backlogged server, and if it was then just use the "current time"+re-schedule time.
____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*