Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Oct 1995 15:56:02 -0700 (PDT)
From:      Brian Litzinger <>
To: (Hinrich Eilts)
Subject:   Solved: hylafax unable to spawn getty with Cardinal 28.8
Message-ID:  <>
In-Reply-To: <199510141152.MAA00431@odin> from "Hinrich Eilts" at Oct 14, 95 12:52:11 pm

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
My original problem:

> > I'm running hylafax on a 2.1 SNAP 951005 with a generic
> > ROCKWELL modem and it mostly works.  However, when
> > I make a data call into the system, the log shows
> > that it spawns getty on the port, put no login
> > ever shows up. I'm using a Cardinal V.34 28.8 modem.

Hinrich Eilts pointed out that he had some problems with getty
being spawned before the CONNECT message from the modem.

Looking into my problem I determined that:

   Yes, indeed, faxgetty was spawning getty before the CONNECT
   message from the modem.  This resulted in getty sending
   'login:' to the modem during the handshake and the modem

   Hylafax has a config option called ModemWaitForConnect which
   is supposed to address this problem.  It doesn't work because:

      Some modems send 

	  CONNECT 38400

      for which the hylafax ModemWaitForConnect works great.
      However, my Cardinal 28.8 is sending:


	  CONNECT 38400

      for which ModemWaitForConnect doesn't work so well.

    Following some more advice from Hinrich, I modified getty
    to wait for the CONNECT message.  I named the waitforCONNECT
    getty fgetty per hinrich's advice, and re-config hylafax
    to invoke fgetty.

All works now.  Happy days.

Thanks to Hinrich Eilts for point me in the right direction.

Disclaimer: I'm not a c++ expert (hylafax is written in c++) so my
opinions of the functionality of the code may be wrong.

Brian Litzinger

Want to link to this message? Use this URL: <>