To all who responded,
Thank you. The response time of this list is excellent.
The concensus for the cause of this problem was a stty command in the
.cshrc or .profile files. The solution was to move the command to the .login
file. The actual responses are listed below.
-----------------------------
casper@holland.Sun.COM:
Looks like a "stty" in a .cshrc someplace.
----------------------------
TrevorPaquette@aec.ca
Check in your .cshrc on the remote machine for an 'stty' command. Maybe you
are resetting your erase key? Anyway, rsh to a remote machine cannot handle
an stty erase command (or antthing that changes the setup of a tty), because
you don't have a tty.
Put the following in your .cshrc around the section for interactive login
sessions.. (ie stty erase ^H)
if ($?prompt) then
stty erase ^H
set history = 100
endif
---------------------------
rali@meitca.com
# if we are running a script, don't source rest of .cshrc.
if (! $?prompt) exit
if (! $?term) exit
---------------------------
matthew.stier@imonics.com
For csh's that would be.
if ( $?prompt ) then
stty sane
endif
--------------------------
simong@aifs.org.au
I think this means you've got an stty command in your .cshrc (or root's
.cshrc). If you take it out and put it in the .login file, I think
that cures it.
--
____________________________________________ _____
/ \ | |
|Kenneth Franco, D450 Electric Boat Company | _________| - |_______
|Systems Engineer 75 Eastern Point Rd. | ||_/ \
|Voice (860)433-4822 Groton, CT 06340 USA | < _ )
|Fax: (860)433-5975 | || \________________________/
|Email: kfranco@plunger.gdeb.com |
\____________________________________________/
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:01 CDT