Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Fw: Fw: Problem with state "waiting for modem to come ready" after sending a fax
Hello Lee,
I think I have discovered two new things:
1) The FaxGetty don't initialize the modem after FaxSend because FaxGetty
don't realize that the ttySx is locked to send this fax. In fact if I kill
the FaxGetty process immediatly after the FaxSend begin his transmission in
the logg appeare the message "FaxGetty[19456]: ANSWER: Can not lock modem
device" (it means that FaxGetty know the ttySx lock) and all perfectly work.
2) I have this problem only with RedHat 7.3. With RedHat 7.2 Hylafax works
well, without any problem.
I say so because I have done a test:
I have firstly installed Redhat 7.2 and then Redhat 7.3 in 6 different
servers, then I have tried hylafax 4.1.3 RPM installation on every server
with 7.2 and 7.3 (I have used the same modems US Robotics 56k Faxmodem and
Rockwell generic).
The result was that hylafax works correctly in all the six redhat 7.2
installation and it provokes the malfunctioning in 5 redhat 7.3
installation. Only one redhat 7.3 installation works fine without problems
(it is an IBM PC300GL).
I think that this is important !
What I have to do in your opinion?
And I am curious, you are an hylafax developer?
Thanks for your help.
Nico.
----- Original Message -----
From: "Lee Howard" <faxguy@howardsilvan.com>
To: <nico@gruppoerrepi.it>
Cc: "Lee Howard" <faxguy@howardsilvan.com>; <hylafax-user@hylafax.org>
Sent: Friday, August 30, 2002 6:46 PM
Subject: Re: [hylafax-users] Fw: Fw: Problem with state "waiting for modem
to come ready" after sending a fax
> On 2002.08.30 08:43 nico@gruppoerrepi.it wrote:
>
> > ago 30 17:25:59 linux2wwp FaxSend[25988]: SEND FAX: JOB 11 DEST
> > 056424997 COMMID 00000011 DEVICE '/dev/ttyS0'
> > ago 30 17:26:40 linux2wwp FaxSend[25988]: SEND FAX: JOB 11 SENT in
> > 0:14
> > Aug 30 17:27:29 linux2wwp FaxGetty[25975]: CAUGHT SIGNAL 15
> > Aug 30 17:27:29 linux2wwp FaxGetty[25975]: CLOSE /dev/ttyS0
> > Aug 30 17:27:29 linux2wwp FaxGetty[25975]: <-- [5:ATH0\r]
> > Aug 30 17:27:34 linux2wwp FaxGetty[25975]: MODEM TIMEOUT: reading line
> > from modem
>
> It would appear that faxsend isn't releasing the FIFO... or dropping
> the lock or something like that. Why do the FaxSend logs say "ago"
> (Italian, I guess) but then the FaxGetty logs say "Aug"?
>
> Anyway, remove the FIFOs, rerun faxsetup and faxaddmodem... figure out
> why faxsend isn't releasing control of the modem back to faxgetty.
>
> 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@hylafax.org <
/dev/null
> *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*
>
>
____________________ 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@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*