[4516] in Athena Bugs
A bug with rlogin
daemon@ATHENA.MIT.EDU (metis@ATHENA.MIT.EDU)
Tue Mar 13 15:09:59 1990
From: metis@ATHENA.MIT.EDU
To: bugs@ATHENA.MIT.EDU
Cc: metis@ATHENA.MIT.EDU
Date: Tue, 13 Mar 90 15:09:43 EST
Program with which you had the problem:
Name of person who discovered the bug: Tom Roby
Their MIT phone number: x3-7557
Their MIT address: 2-233
Their Athena Login ID: metis
Name of consultant reporting bug: metis
------------------------------------------------------------------------
A brief synopsis of the problem: rlogin.ucb doesn't seem to work
properly from this pmax; it complains that I'm not using the correct
syntax (which I am).
------------------------------------------------------------------------
Please describe the problem in detail (mention any necessary files or
commands that may be involved, on which machine the bug happened, and what
the program did that was wrong):
Here's the session. I have rlogin aliased to "rlogin.ucb".
(REPOMAN.MIT.EDU)/mit/metis[4]% rlogin turing
usage: rlogin host [ -ex ] [ -l username ] [ -8 ] [ -L ]
(REPOMAN.MIT.EDU)/mit/metis[5]% rlogin taylor.mit.edu
usage: rlogin host [ -ex ] [ -l username ] [ -8 ] [ -L ]
(REPOMAN.MIT.EDU)/mit/metis[6]% hostinfo taylor
Desired host: taylor
Official name: TAYLOR.MIT.EDU
Host address: 18.87.0.72
(REPOMAN.MIT.EDU)/mit/metis[7]% where rlogin
rlogin is aliased to rlogin.ucb
/usr/ucb/rlogin
(REPOMAN.MIT.EDU)/mit/metis[8]% rlogin taylor
usage: rlogin host [ -ex ] [ -l username ] [ -8 ] [ -L ]
(REPOMAN.MIT.EDU)/mit/metis[9]% \rlogin taylor
TAYLOR.MIT.EDU: Connection refused
rlogin: Kerberos rcmd failed: rcmd protocol failure.
trying normal rlogin (/usr/ucb/rlogin.ucb)
Password:
Last login: Mon Mar 5 15:52:47 from riesz.mit.edu
SunOS Release 4.0.3c (GENERIC) #1: Thu May 25 17:17:12 PDT 1989
As you can see, when I did the standard "rlogin" command, it fell back
to /usr/ucb/rlogin, and that time it worked properly. This I don't
understand.
------------------------------------------------------------------------
Repeat by (please enter a set of commands which will allow us to
repeat the bug):
See the above session.
------------------------------------------------------------------------
Fix (if you know what it is):
No clue.
