[hylafax-users] faxgetty stampede

[ignace.suy@dutchtone.nl]

Folks,
When receiving a fax on my system, faxgetty takes as much system resources
as it needs and never lets go again, until i kill the process. It does never
finish the receiving job.
All goes well until the first set of data is received. A few seconds after
that point, the sending side (also hylafax) claims the receiving site has
terminated the connection prematurely. While receiving, you see the normal
logging until:
<snip>
Aug 28 07:57:01.59: [  775]: REMOTE wants 14400 bit/s
Aug 28 07:57:01.59: [  775]: REMOTE wants page width 1728 pixels in 215 mm
Aug 28 07:57:01.59: [  775]: REMOTE wants unlimited page length
Aug 28 07:57:01.59: [  775]: REMOTE wants 7.7 line/mm
Aug 28 07:57:01.59: [  775]: REMOTE wants 2-D MR
Aug 28 07:57:01.59: [  775]: --> [7:CONNECT]
Aug 28 07:57:01.59: [  775]: RECV: begin page
Aug 28 07:57:01.59: [  775]: RECV: send trigger 022
Aug 28 07:57:01.59: [  775]: <-- data [1]
Aug 28 09:47:28.89: [  775]: CLOSE /dev/ttyS0      #after killing faxgetty 
<snip>
This is a class 2 modem, but class 1 usage gets similar results, If I
exchange modems (differend brands) with another "fax-box" i get the same
problems. The sending process works just fine. I am using Hylafax 4.1beta2
On SuSE 6.4.
The mailarchive list a similar thing (now faq102) with faxq, but i cannot
match this with my case.
I am running an earlier version on SuSE 6.1 on another box - no problems
there...but installing that suse hylafax build makes no sense because its
uses differend libraries.

Any suggestions?


Ignace Suy



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null