On Sun, Dec 24, 2006 at 01:06:12PM +0100, Giuseppe Sacco wrote: > Hi Paolo, > I dont know if you noticed what upstream added to this report. Please > have a look at the messages in > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369759 and let me know > if it is okay for you to close this bug report.
sorry, I thought I've already replied, but either no/lost or to other list. Anyway, the example offered is quite different from my case. I understand how the -k opt can be used to manage a high-P job, but I'm not clear on how to combine sendfax's avail opts to handle my case, ie per-destination limits on send-list. It might be that I just don't understand fully sendfax(1) opts - examples welcome :). BTW sendfax.1 says -k starts from 'time is relative to the time of the initial time-to-send.' - should make clearer that that means, for a send-list, the TTS of the first attempt for the 1st destination, not the per-destination TTS. Shortly, the explanation offered doesn't seem to conver bug-report case, hence bug is still there imo, unless meanwhile sendfax(1) behaviour has changed (haven't had other very-long send-list cases). thanks -- paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
