From owner-freebsd-questions  Sat Oct 14 15:58:21 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA21582
          for questions-outgoing; Sat, 14 Oct 1995 15:58:21 -0700
Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA21577
          for <questions@freebsd.org>; Sat, 14 Oct 1995 15:58:19 -0700
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id PAA09529; Sat, 14 Oct 1995 15:56:02 -0700
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199510142256.PAA09529@MediaCity.com>
Subject: Solved: hylafax unable to spawn getty with Cardinal 28.8
To: eilts@iwte01.dialin.rrze.uni-erlangen.de (Hinrich Eilts)
Date: Sat, 14 Oct 1995 15:56:02 -0700 (PDT)
Cc: questions@freebsd.org
In-Reply-To: <199510141152.MAA00431@odin> from "Hinrich Eilts" at Oct 14, 95 12:52:11 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Content-Length: 1502      
Sender: owner-questions@freebsd.org
Precedence: bulk

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
   disconnecting.

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

      Some modems send 

	  DATA
	  CONNECT 38400

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

	  DATA

	  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
brian@mediacity.com