Item Subject: Message text
Kim and Chris said:
> > Any machine trying to rlogin to the new upgraded AFS client 'chopin'
> > meets the following error message:
>
> > rlogind: /dev/ttyp4: Not owner.
> > Connection closed.
>
>
> I've seen this too on Solaris 2.4.
>
> Furthermore I can't get remote authentication thru rsh to solaris
> machines to work either. It works, however, to the pmax machines.
>
> There seems to be some work left to do on AFS3.4.
Tell me about it. I've seen both these problems (on AIX 4.1 too) and
reported them to Transarc as a bug in the 3.4 Beta. They say it will be
fixed in the GA release. Generally we have problems with the transarc
supplied versions of the 'r' commands. We have a very mixed environment
with Sun, Dec, IBM, SGI and other hardware on a variety of operating
systems. We have found a number of incompatabilities, and some very
peculiar behaviour if you mix the kerberised versions on some machines
with the vanilla version on others (which is probably not a sensible thing
to try to do anyway).
Our problems /include/: rlogind doesn't work with 33a and Solaris 2.3
(rlogind binary missing) or with 3.4 and Solaris 2.4. With 3.4 and Solaris
2.4 rlogin hangs if you do it from root. We need to use the Transarcian
login so we tried running that with vanilla rlogin. Then when you rlogin
some machines prompt for the passwd, but then say
"Unable to read password because can't read password from terminal.
Login incorrect
login:"
A second attempt to login works.
These kinds of problems are relatively minor (well, at least it's not a
cache corruption bug, your data's still OK, ha ha ha only serious) but
really irritating to users. Bugs like this smell of a lack of testing to
me, particularly when similar bugs were reported in 33a and 3.4 was meant
to fix them.
Has anyone managed to get kerberised login, rlogin, rsh and ftp working in
a multivendor environment? If so, what did you do, port FreeBSD? Can I
have a copy?
Thanks,
Andy Haxby
/* Shell Research, KSEPL Netherlands */
