![]() |
This has been broken for a LONG time; I reported this as a problem more than two years ago and I am not surprised if it is STILL broken, as I don't recall anything in release notes indicating that it has been found and fixed. It essentially prevented me from using Hylafax for batch delivery of invoices and such at my former company, since the system would queue all of them at once and invariably a huge number of them would get killed by the scheduler without ever being attempted. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net Cost-effective Consulting http://childrens-justice.org SIGN THE UPREPA PETITION TODAY On Thu, Mar 14, 2002 at 02:36:33PM -0800, Lee Howard wrote: > On 2002.03.14 09:24 Sid Lambert wrote: > > I am sending faxes via a script using the following line. > > sendfax -t 3 -k 240 -n -h cuaa0@localhost -d many_numbers file.ps > > > > I have around 7k faxes to send and it seems to kill all the jobs > > remaining > > after about 12 hours even though I have it set to 240 hours. Am I missing > > something? > > > > This is the killtime value from a fax in sendq: killtime:1016177987 > > what happens if you use > > -k "now + 240 hours" > > ?? > > Lee. > > ____________________ HylaFAX(tm) Users Mailing List _______________________ > To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null > ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null