Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Oct 1995 17:28:47 -0700 (MST)
From:      Terry Lambert <terry@lambert.org>
To:        brian@MediaCity.com (Brian Litzinger)
Cc:        questions@freebsd.org
Subject:   Re: hylafax unable to spawn getty
Message-ID:  <199510140028.RAA18746@phaeton.artisoft.com>
In-Reply-To: <199510140003.RAA17478@MediaCity.com> from "Brian Litzinger" at Oct 13, 95 05:03:57 pm

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> 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?

How about "nothing".

1)	getty's open doesn't complete until DCD goes high.

2)	getty puts out the /etc/issue (if you have a good getty),
	the login prompt from the gettytab, and then waits for
	input.  Or a break character, which causes it to rotor
	through the baud rate list.

3)	After you type in a name, getty exec's login with the name,
	and login asks for the password.

4)	(optional) if the  login fails, login, not getty, issues the
	next "login: " prompt.  That's why the initial and subsequent
	prompts are different.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?199510140028.RAA18746>