![]() |
At 12:27 PM 4/12/01 -0500, Dennis Fellows wrote: >OK, OK, I'll upgrade like you suggest. :) >This isn't a production machine (yet) so I can make the upgrade without fear >of breaking something. >Apr 12 06:27:55.76: [ 944]: RECV: send trigger 022 >Apr 12 06:27:55.76: [ 944]: <-- data [1] >Apr 12 07:49:19.61: [ 944]: CLOSE /dev/ttyR0 >DialStringRules: etc/dialrules >ServerTracing: 1 >SessionTracing: 11 >RecvFileMode: 0600 We can't tell what's going on because SessionTracing isn't at 0xFFF. But, if I were to bet, it was doing the +FRH=3, <Empty Line> endless looping. This has been an occasional issue off and on since at least beta1 days (as I experienced it once or twice then myself) and someone will mention this ever so often on the list. It seems like you restart faxgetty, and all will be fine for quite a while. The best explanation that I have heard of it is that it's caused by modem Class 1 firmware "bugs". But if you ask me, it's a HylaFAX bug that doesn't terminate the session after it's obvious that the carrier is not returning. Lee. ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null