Date: Sat, 14 Oct 1995 15:56:02 -0700 (PDT) From: Brian Litzinger <brian@MediaCity.com> To: eilts@iwte01.dialin.rrze.uni-erlangen.de (Hinrich Eilts) Cc: questions@freebsd.org Subject: Solved: hylafax unable to spawn getty with Cardinal 28.8 Message-ID: <199510142256.PAA09529@MediaCity.com> 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
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510142256.PAA09529>