Subject: Getty hell
To: None <>
From: Stephen Anspach <>
List: amiga
Date: 12/06/1994 17:10:00
  I'm losing hair rapidly while trying to get serial logins configured on
tty00.  I have a USR28.8K on port 0 of a MultifaceIII card (tty02) and an
Intel <yuk> 14.4K on tty00.  The (apparent) problems are as follows:

  I can't seem to get anything to read /etc/uucp/Dialers for an init string.
The file needs to be there, or nothing will function (obviously).  


ACU tty00 - 19200 intel
ACU tty01 - 38400 hayes
ACU tty02 - 38400 hayes


hayes	=,-,	"" \dA\pTE1V1X1Q0S2=255S12=255\r\c OK\r \EATDT\T\r\c CONNECT
#intel	=,-,	"" \dA\pTE1V1X1Q0S2=255S12=255\r\c OK\r \EATDT\T\r\c CONNECT
intel ATZ\r

  Whatever I seem to change these to doesn't matter - it seems like it's
never read.  The format is from a "stock" file on a BDSI system.


console	"/usr/libexec/getty Pc"		vt200	off secure 
ttye0	"/usr/libexec/getty Pc"		vt200	on secure 	# custom chips
tty00	"/usr/libexec/getty std.19200"	dialin  on secure	# int. serial.
#tty01	"/usr/libexec/getty std.19200"	unknown off secure	# mfc3 port 0
#tty02	"/usr/libexec/getty std.19200"	unknown off secure	# mfc3 port 1

  I've tried changing to std.9600 and different tty types with no effect.


	:ap:fd#1000:im=\r\n%s/%m (%h) (%t)\r\n\r\n:sp#1200:


  I can't find any fault with my cfg files, with the exception of the init
problem in Dialers.  Am I missing something? (I have little to no experience
with UUCP)  BTW, the port works fine for dialout via cu, kermit, etc. if
flagged to off in ttys.

  If I set the modem to E1, the send & receive lights stay on solidly, except
during disk access (?), when they correspond to the drive light.  Also, getty
spawns a login process immediately, with a hunk of my login prompt
("NetBSD/amiga (xor) login:") as input.  This shows up as something on the
order of "login -p iga (xor" in the process list.
  When set to E0, things look much better - the send/receive lights are off,
and getty doesn't always spawn a login when nothing's there.  It happily sits
and waits, but then upon connect, I once again get a login with crap.
  It seems obvious that for some reason the info being sent over the line
gets echoed back and is picked up as input, but I can't figure out why.
  I get good connects with proper "CONNECT 14400 etc" messages on the
caller's end, but just garbage ("~~~ff") after that and nothing I type is
echoed back.

  Can anybody suggest where my problem may lie?  Thanks in advance...

                                    - Steve -

Internet		FidoNet    1:102/852.6

Quis custodiet ipsos custodes?