Re: problem with inbound data calls

[Matthias.Apitz@SOFTCON.de (Matthias Apitz)]

I've seen many questions like this and also some strace(1)-output
logs where the Linux's getty(1M) closes all file descriptors, also
the descriptor for stdin which is the modem line and given to getty(1M)
from the faxgetty(1M) proc after detecting the call as a DATA call.
in such situation (closing all descriptors for the modem line) a HANGUP
is the bad but normal result.

I think it's time to track this down and write a page/scorecard
how and which getty(1M) should be used on the various Linux versions.
It belongs to the FAQ (but I'm not using Linux).

	matthias

Jim Alumbaugh wrote:
    
    
    I'm using Hylafax v4.0pl1 on Linux Redhat distribution 4.0 with gcc 
    2.7.2; USROBOTICS SPORTSTER 28800 V.34 modem.
    
    We previously had Linux Redhat 2.0 and an older version of Hylafax 
    installed and working properly, but then we upgraded to Redhat 4.0.  
    Thus, I had to download and rebuild Hylafax after upgrading to 4.0.
    
    Since rebuilding and reinstalling Hylafax, I haven't been able to get 
    FaxGetty to handle inbound data calls correctly.  Everytime I try to 
    make a connection, I am originally connected, but then the line hangs 
    up soon afterwards.  Here's what the session usually looks like:
    
    CONNECTED 38400 CAA
    
    NO CARRIER
    
    Here's what showing up in the log files:
    
    ----- (from /var/log/messages):
    Feb 20 13:58:13 cal FaxGetty[6394]: ANSWER: DATA CONNECTION
    Feb 20 13:58:13 cal FaxGetty[6394]: GETTY: START "/sbin/getty -h -- -
    38400", pid 17086 Feb 20 13:58:13 cal getty[17086]: open failed on
    "/dev/-": No such file or directory Feb 20 13:58:13 cal
    FaxGetty[6394]: GETTY: exit status 0177400 Feb 20 13:58:18 cal
    FaxGetty[6394]: MODEM USROBOTICS SPORTSTER 28800 V.34 FAX Product type
              US/Canada Internal Options                V 32bis,V.FC,V.34
    Fax Options            Class 1/Class 2.0 Clock Freq            
    20.16Mhz Eprom                  256k Ram                    32k/
    Supervisor date        04/18/95 DSP date               03/31/95
    Supervisor rev         6.0.5 DSP rev                1.0.9
    ------------(end)
    
    or ...
    
    ----------(begin)
    Feb 20 13:59:46 cal FaxGetty[6394]: ANSWER: DATA CONNECTION
    Feb 20 13:59:46 cal FaxGetty[6394]: GETTY: START "/sbin/getty ttyS2
    38400", pid 17092 Feb 20 13:59:46 cal getty[17092]: exiting on HANGUP
    signal Feb 20 13:59:46 cal FaxGetty[6394]: GETTY: exit status 0 Feb 20
    13:59:52 cal FaxGetty[6394]: MODEM USROBOTICS SPORTSTER 28800 V.34 FAX
    Product type           US/Canada Internal Options                V
    32bis,V.FC,V.34 Fax Options            Class 1/Class 2.0 Clock Freq   
             20.16Mhz Eprom                  256k Ram                   
    32k/ Supervisor date        04/18/95 DSP date               03/31/95
    Supervisor rev         6.0.5 DSP rev                1.0.9
    -----(end)
    
    In the first example, it looks as if getty is having problems 
    finding ttyS2.  I've tried changing the GettyArgs configuration a 
    number of times, but nothing has worked.  Here's what I currently 
    have:
    
    ------(from /var/spool/fax/etc/config.ttyS2)
    GettyArgs:              "-h -- - %s"
    
    ------(end)
    
    Also, I'm not quite sure about my entry in inittab.  Here's what I 
    have:
    
    -------(begin /etc/inittab)
    
    t2:2345:respawn:/usr/local/sbin/faxgetty ttyS2
    
    ----------(end)
    
    Anyone have any ideas as to the solution to my problem, or additional 
    sources I can investigate?
    
    Thanks very much for any help you can offer.
    
    -Jim
    
    ---------
    Jim Alumbaugh                   jim@alumni.berkeley.edu
    Manager, Information Systems    jima@cal.alumni.berkeley.edu
    California Alumni Association   (510) 643-6897
    Alumni House
    Berkeley, CA  94720