danny@idacom.uucp (Danny Wilson) (12/23/89)
After installing SR10.1 we are experiencing strange problems with rlogin locking up. This problem only happens if you rlogin 'two deep', which means in our case: apollo1 --rlogin-> sun1 --rlogin-> sun2 If you do this, after the rlogin to 'sun2', no characters are echoed on the original apollo. Keystrokes are properly passed to 'sun2' and commands can be executed if you terminate the command with a LINEFEED instead of a CR. When you press LF, the command is echoed 'in toto' and the output from the command is visible. This problem does not happen with: sun0 --rlogin-> sun1 --rlogin-> sun2 or, apollo0 --rlogin-> apollo1 --rlogin-> apollo2 Anyone know what is is going on?? PH (Possible Hint) #1 When you rlogin to 'sun1' first a '!' character is printed; a second later, the login message from the Sun is printed. This does not happen in any other circumstance PH#2 After connected to sun2, 'stty sane', 'reset' or 'tset' commands do not fix the problem any. -- Danny Wilson danny@idacom.uucp IDACOM Electronics alberta!idacom!danny Edmonton, Alberta X.400 danny@idacom.cs.ubc.cdn C A N A D A Voice +1 403 462 4545
danny@idacom.uucp (Danny Wilson) (12/28/89)
After installing SR10.1 we are experiencing strange problems with rlogin locking up. This problem only happens if you rlogin 'two deep', which means in our case: apollo1 --rlogin-> sun1 --rlogin-> sun2 If you do this, after the rlogin to 'sun2', no characters are echoed on the original apollo. Keystrokes are properly passed to 'sun2' and commands can be executed if you terminate the command with a LINEFEED instead of a CR. When you press LF, the command is echoed 'in toto' and the output from the command is visible. This problem does not happen with: sun0 --rlogin-> sun1 --rlogin-> sun2 or, apollo0 --rlogin-> apollo1 --rlogin-> apollo2 Anyone know what is is going on?? PH (Possible Hint) #1 When you rlogin to 'sun1' first a '!' character is printed; a second later, the login message from the Sun is printed. This does not happen in any other circumstance PH#2 After connected to sun2, 'stty sane', 'reset' or 'tset' commands do not fix the problem. -- Danny Wilson danny@idacom.uucp IDACOM Electronics alberta!idacom!danny Edmonton, Alberta X.400 danny@idacom.cs.ubc.cdn C A N A D A Voice +1 403 462 4545
danny@idacom.uucp (Danny Wilson) (01/16/90)
(Sorry if you've seen this before... I just discovered it sitting in my 'dead.article' file) After installing SR10.1 we are experiencing strange problems with rlogin locking up. This problem only happens if you rlogin 'two deep', which means in our case: apollo1 --rlogin-> sun1 --rlogin-> sun2 If you do this, after the rlogin to 'sun2', no characters are echoed on the original apollo. Keystrokes are properly passed to 'sun2' and commands can be executed if you terminate the command with a LINEFEED instead of a CR. When you press LF, the command is echoed 'in toto' and the output from the command is visible. This problem does not happen with: sun0 --rlogin-> sun1 --rlogin-> sun2 or, apollo0 --rlogin-> apollo1 --rlogin-> apollo2 Anyone know what is is going on?? PH (Possible Hint) #1 When you rlogin to 'sun1' first a '!' character is printed; a second later, the login message from the Sun is printed. This does not happen in any other circumstance PH#2 After connected to sun2, 'stty sane', 'reset' or 'tset' commands do not fix the problem. -- Danny Wilson danny@idacom.uucp IDACOM Electronics alberta!idacom!danny Edmonton, Alberta X.400 danny@idacom.cs.ubc.cdn C A N A D A Voice +1 403 462 4545
dbfunk@ICAEN.UIOWA.EDU (David B Funk) (01/16/90)
In posting <1990Jan15.193322.8358@idacom.uucp>, Danny Wilson <danny@idacom.uucp> asks: > After installing SR10.1 we are experiencing strange problems > with rlogin locking up. > ... It sounds like your pseudo-ttys ("/dev/?typ?") are messed up. I've seen some strange problems caused by messed up device files. Try deleting all the pseudo-tty files and then using "/etc/crpty" to recreate a fresh batch. I had one case where a sour OS install messed up lots of the stuff in /dev. None of the user processes knew what their "TTY" was. (IE you'd do a "ps agux" and ALL the processes had a "?" in their "TTY" field.) I had to delete everything out of /dev and use /etc/mkdev to recreate it all. Dave Funk