Dear AFSers...

        Yesterday I questioned about 'rlogind' error that we found out when 
upgrading AFS 3.3 to AFS 3.4 beta yesterday. Some answers reached me, 
but I think they are not quite helpful. ( anyway, thanks Tom and Bill, ^_^ )

        So here I'd like to summarize our problem and re-question it.

        1) We're upgrading AFS client from version 3.3 to version 3.4 beta.

        2) All the installations finished successfully.

        3) 'login' and 'rlogind' were replaced for AFS authentications.

        4) Now 'login' works fine but 'rlogin' to the upgraded host fails 
with the following error messages:

                rlogind: /dev/ttyp4: Not owner.
                Connection closed.

        5) But, rlogin as ROOT does work! 'rlogin [host] -l root' doesn't
produce the error.

        Before upgrading we didn't see such errors with 'rlogind'. Here are 
the system status;

        [BEFORE]

        in /etc/inetd.conf ...

        login   stream  tcp     nowait  root    /usr/etc/rlogind        rlogind

        in /usr/etc ... this is AFS 3.3 version of rlogind.

        144 -rwxr-xr-x  1 root       139264 Oct 19 17:00 rlogind*

        [NOW]

        in /etc/ined.conf ... we didn't change any line, same as the above.

        in /usr/etc ... this is AFS 3.4 version of rlogind.

        264 -rwxr-xr-x  1 root       262144 Oct 18 21:58 rlogind*


        Any other things were exactly SAME in our AFS client. But in [BEFORE]
rlogin works, in [NOW] it doesn't. I can't help thinking it is caused by
a binary BUG of the new 'rlogind'. Any idea? Help me... 


___________________________________________________________________________

 |  *   *  **  *   *  **    |     Remember Yesterday,
 |   * *  *  *  * *  *  *   |     Dream about Tomorrow,
 |    *   *  *   *   *  *   |     but
 |_   *   *  *   *   *  *  _|     LIVE TODAY !!!
((_)  *    **    *    **  (_))                       --- yoyo's motto

        [EMAIL PROTECTED] (Jae-young Kim)
        Tel) 0562-279-5655 (Networking and Distributed Systems Lab.)
___________________________________________________________________________

Reply via email to