🚀 go-pugleaf

In article <4493.673892396@dblues.wpd.sgi.com>, jackr@dblues.wpd.sgi.com (Jack Repenning) writes:
|> 
|> Recently, Minh Tran-Le wrote:
|> 
|> 	I have seen that strange message "`tty`: Ambiguous" when you
|> 	try to use `rsh' on an hp machine.  The `rsh' is the
|> 	restricted shell program and not the remote shell.  The remote
|> 	shell is `remsh'.
|> 
|> But I assume you never figured out what was causing it?
|> 
|> An interesting aspect of this comment is that rsh is a restricted form
|> of the Bourne shell, or of the Korn shell if you have that installed:
|> these shells don't necessarily read any set-up files, whereas csh
|> always reads ~/.cshrc, and so a "tty: Ambiguous" message from them is
|> less likely to be related to set-up files.
|> 
The message is in fact coming from a .cshrc.  The tty command returns
"not a tty" and a case statement is trying to use that data to decide 
whether or not do do something like bring up windows.  The fix for it
is to get rid of any session start up code in .cshrc.  Cshrc should do 
things like setting envirments and aliases, not setting terminal
characteristics, or starting window systems.

Cheers

Earl Stutes