![]() |
* Markus Kahle <markus.kahle@xxxxxxxxxxxxxxxxxx> [071211 03:33]: > Hi Aidan, > > Those fax-ids are faxes which all originally scheduled for friday,21th > of December. That's because for our intended use we had to deal with > some hylafax shortcomings in case of setting a fax "on hold". Till now > it's not possible to commit a fax to hylafax "on hold" , so you have to > explictly activate this fax again by using faxalter or via avantfax webpage. > So we did a work-around for this problem by setting a 2 weeks delay on > these faxes, this explains those high tts and killtimes of 5532, 5530, > 5477, 5476 and 5478. Ah - I've reproduce it by submitting jobs way in the future. Give me some time, and I'll see if I can get it fixed. > Does hylafax has problems with those high tts and killtimes ? It's not *supposed* too... > As mentioned we used this "two weeks" delaytime in tts and killtime to > simulate "on hold" status. > > Is the hylafax scheduler getting confused by those high tts & killtimes > so even faxes with earlier tts times got blocked ? This would explain > our problems, but hylafax should get into troubles even with 2 weeks tts > & killtimes, shouldn't it ? > > Are there any other options to get a "on hold" function to work in > hylafax and what's the highest tts & killtime hylafax scheduler is > supporting right now ? I've used the following scheme to "hold" jobs for times.. It's not quite the same as what your doing, but similar: http://people.ifax.com/~aidan/hylafax/jobcontrol/jobcontrol-queue.sh.txt a. -- Aidan Van Dyk aidan@xxxxxxxx Senior Software Developer +1 215 825-8700 x8103 iFAX Solutions, Inc. http://www.ifax.com/ ____________________ 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*