Path: utzoo!mnetor!uunet!ccicpg!turnkey!stanton!donegan
From: donegan@stanton.TCC.COM (Steven P. Donegan)
Newsgroups: comp.unix.xenix
Subject: Re: tty error
Message-ID: <3@stanton.TCC.COM>
Date: 6 Apr 88 03:16:38 GMT
References: <884@udccvax1.acs.udel.EDU> <160@turnkey.TCC.COM>
Distribution: na
Organization: Stanton Public Domain Systems, Stanton, Ca.
Lines: 26
Summary: GETTY death - I've experienced it too...

In article <160@turnkey.TCC.COM>, jack@turnkey.TCC.COM (TCC Software Developer) writes:
In article <884@udccvax1.acs.udel.EDU> mabrey@vax1.acs.udel.EDU (Dennis W Mabrey) writes:
>
>        The company I work for has an AT compatable running         
>        SCO XENIX.   We sometimes get the message on our main console 
>        that says:
> 
>       init:/dev/ttyx05: getty keeps dying. There may be a problem 
I too have had getty die, one thing I've noted is that a terminal connected
as a non-modem (such as a 'm' gettydef code in /etc/ttys) can have serious
problems if the device/terminal is powered off while physically connected to
the PC's serial port. My 'fix' to this gettydeath has been simply powering
off the terminal, doing an /etc/haltsys, powering off the PC, waiting the
required 30 seconds for the power supply to bleed off and then re-starting
the terminal, PC, XENIX etc. This cycle always works for me. Seems that the
8250 or 16450 chip gets lost in space somewhere and XENIX's getty doesn't
know or try a full reset when it dies...sigh
If you had a REAL computer (like a cray, doesn't everyone need one at home?)
this WOULDN'T HAPPEN! :-)

donegan@stanton

-- 
Steven P. Donegan
Sr. Telecommunications Analyst
Western Digital Corp.