RE: flexfax: Maxtries > 12, MaxDials > 12

["Mau, Jonathan" <Jonathan.Mau@nrc.ca>]

	> All my client really wants is for the jobs to not fail so quickly
so they
	> have a chance to give the client a ring and tell  them their
machine is out
	> of paper or whatever.  They want the jobs to be alive for 2 days.
I am now

	A better strategy, in that case, would be to increase the interval
between
	retries.  I haven't checked if this is a configuration option, but,
if
	not, it will be a trivial code change, not requiring any real
knowledge
	of C++.

Thank you for your comments David.  Yes, that is the track I am on now.  I
have set (on January 31 I believe) the following parameters in faxd config
file:

JobReqBusy:		14400
JobReqDataConn:	14400
JobReqNoAnswer:	14400
JobReqNoCarrier:	14400
JobReqNoFCon:		14400
JobReqOther:		14400
JobReqProto:		14400

In plain English, I want any and all failures to retry in 4 hours.

It is not at all clear what faxd is doing.  Some reschedules are 4 or 5
hours into the future, but others are a few minutes.  I still get jobs that
get a busy and dial every 3 or 4 minutes until they expire on
Dial=MaxDials=12 after a total elapsed time of less that an hour.
JobReqBusy should have set this to 4 hours.  An example from my log files is
below.  This file was generated by a customized notify script (instead of
the default behaviour of sending email messages).

See how the system reschedules every few minutes on busys until all of a
sudden the reschedule time is 6 hours into the future on the ring detect
error.  Now granted I don't expect to see exactly 4 hours here because the
times here are dependant on how busy is the system, but remember, this job
has failed 4 or 5 times so its priority has been advancing and a 2 hour
delay is not believable.

Can anyone explain this?

Jonathan


2000/02/02 11:35:15 00463575N00123669 REQUEUED      Busy signal detected
2000/02/02 11:39:24 00463575N00123669 REQUEUED      Busy signal detected
2000/02/02 11:43:20 00463575N00123669 REQUEUED      Busy signal detected
2000/02/02 11:48:04 00463575N00123669 REQUEUED      Ring detect without
successful handshake
2000/02/02 17:04:46 00463575N00123669 REQUEUED      Busy signal detected
2000/02/02 17:13:12 00463575N00123669 REQUEUED      Ring detect without
successful handshake
2000/02/02 21:05:13 00463575N00123669 REQUEUED      Ring detect without
successful handshake
2000/02/03 02:01:17 00463575N00123669 REQUEUED      Busy signal detected
2000/02/03 02:05:05 00463575N00123669 REQUEUED      Busy signal detected
2000/02/03 02:08:53 00463575N00123669 REQUEUED      Busy signal detected
2000/02/03 02:12:41 00463575N00123669 REQUEUED      Busy signal detected
2000/02/03 02:16:28 00463575N00123669 REQUEUED      Busy signal detected
2000/02/03 02:19:23 00463575N00123669 REJECTED      REJECT: Too many
attempts to dial: 12, max 12