HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] a quickie
Actually, that sounds a little different to what I'm experiencing. Maybe
I didn't use the correct terminology.
I'm seeing all the Blocked jobs (say in WHFC, with a 'B' State and a
status of 'Blocked by concurrent calls', but they just stay there
forever or until I restart Hylafax in which case one of the Blocked jobs
gets sent but the remainder stay Blocked again forever, until the next
time I restart Hylafax and then again only the next Blocked job is sent,
but the remainder always stays blocked.
Is this the problem that is a known bug, or do I have a unique situation
on my hands?
Also, how is batching enabled/disabled or how can I check the status of
this?
What I'd really like is for the concurrent call blocking to be
completely gone. i.e. I don't care that Hylafax thinks it's a concurrent
call (in my case all these blocked calls are handled by a virtual line
that does it's own queueing anyway). I have set MaxConcurrentJobsS* to
9999 for every ttyS* but no difference...
Thanks,
Pete
-----Original Message-----
From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
Sent: Friday, 9 February 2007 12:23 PM
To: hylafax-user
Cc: Peter Verhoeven
Subject: Re: [hylafax-users] a quickie
Darren Nickerson wrote:
> I'll follow-up to the list once we have an explanation for what you're
> seeing.
It's probably this:
http://hylafax.cvs.sourceforge.net/hylafax/hylafax/faxd/faxQueueApp.c%2B
%2B?view=log#rev1.39
Patch here:
http://hylafax.cvs.sourceforge.net/hylafax/hylafax/faxd/faxQueueApp.c%2B
%2B?r1=1.38&r2=1.39&view=patch
The problem was that the unblockDestJobs function was unaware that
di.getBlocked() actually removed the job from the blocked list.
Consequently, if the case arose that it couldn't place that job on the
run queue (much more likely if batching were disabled, I'd think) then
unblockDestJobs would erroniously not replace the job back onto the
blocked list. So from then on that job would have "disappeared" from
faxq altogether until faxq were stopped and restarted when it creates
the lists anew from the sendq files on disk.
Lee.
____________________ 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*