From owner-freebsd-questions  Fri Oct 13 16:58:27 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA17223
          for questions-outgoing; Fri, 13 Oct 1995 16:58:27 -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 QAA17217
          for <questions@freebsd.org>; Fri, 13 Oct 1995 16:58:25 -0700
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id RAA17478 for questions@freebsd.org; Fri, 13 Oct 1995 17:03:58 -0700
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199510140003.RAA17478@MediaCity.com>
Subject: hylafax unable to spawn getty
To: questions@freebsd.org
Date: Fri, 13 Oct 1995 17:03:57 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Content-Length: 587       
Sender: owner-questions@freebsd.org
Precedence: bulk

I'm running hylafax on a -current system with ZyXEL 1496E
and it works great.

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 can see (via ps)  getty on the right port
just sitting there.  It sits there until I kill the getty
at which point I get hung up upon and the hylafax system
takes over again.

On both systems I'm using /dev/cuaa0.

Any ideas what is wrong?

Thanks,

Brian Litzinger
brian@mediacity.com