Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!n8emr!uncle!donlash
From: donlash@uncle.uucp (Donald Lashomb)
Newsgroups: comp.sys.3b1
Subject: Re: stty: : Not a typewriter
Message-ID: <1991Mar11.195232.19266@uncle.uucp>
Date: 11 Mar 91 19:52:32 GMT
References: <1495@das13.snide.com>
Organization: U.N.C.L.E.
Lines: 23

In article <1495@das13.snide.com> dave@das13.snide.com (Dave Snyder) writes:
>That's the error message I get while doing various things on my machine.
>
[...]
>stty: : Not a typewriter
[...]
>Anyone have any ideas?

Are you using ksh?  If so, check your ENV file ($HOME/.kshrc) for the
stty command.  Whenever ksh starts up, it reads and executes its ENV
file.  Many people put stty and other like commands in there.  However
when ksh is run unconnected to a tty, these commands fail with the
error message you see.  The answer to this problem is to isolate the
stty command in ENV by testing ksh's "$-" variable.  eg:

	case $- in
	*i*)	# interactive ksh
		stty sane
		;;
	esac

Hope this helps,
Don			donlash@uncle.UUCP