Hylafax Mailing List Archives |
On 2003.12.05 12:57 Aidan Van Dyk wrote:
So, it definately seems like it's stuck in a system call. It seems it's not actually "doing" anything (CPU wise), correct?) The output of strace should be able to tell us what system call it's doing.
From my earlier analysis, I believe that faxgetty is looping in ModemServer::getModemLine() for the modem to respond with +FPS. The modem never does respond with +FPS, however (so a Class 2 firmware bug is triggering a HylaFAX problem here). ModemPageDoneTimeout is supposed to control how long faxgetty waits in getModemLine(), but ModemPageDoneTimeout doesn't seem to be working - so we loop forever waiting for +FPS.
ModemPageDoneTimeout is, by default, exceptionally large, 180000. I don't know if that has some factor on this (perhaps because it exceeds a 16-bit integer size), so that's why I've asked them to test with ModemPageDoneTimeout set to 60000.
Lee.
I did this, I patched libfaxserver.so.4.1.7 with the debug patch and I will do a stack trace on faxgetty process when problem arises.
____________________ 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@xxxxxxxxxxxx*
|