Hi, What's the deal with the woody versions of rlogin / rsh? Although nis is working wonderfully, that's node01:~# ypcat netgroup (borg,,) (node01,,) (node03,,) (node04,,) (node05,,) (node06,,) (node07,,) (node08,,)(node09,,) (node10,,) (node11,,) (node12,,) (node13,,) (node15,,)(node16,,) (node18,,) (node19,,) (node20,,) (node21,,) (node22,,)(node23,,) (node24,,) (node25,,) (node27,,) (node28,,) (node29,,) (node30,,) (node31,,) (node32,,) (node33,,) (node34,,) (node35,,) (node36,,) node01:~# ypcat passwd [passwd dump] ....
works, I can't login to nis slave machines. Is this because of login? or because of rsh itself or perhaps even PAM, do you have any idea? :( The same setup used to work on potato, so might this be related to the wonderful new glibc? The setup is very simple. This is a beowulf comprised of 1 master and 32 slave nodes. rsh/rlogin works across nodes, each node has others listed in .rhosts [EMAIL PROTECTED]:~$ cat .rhosts [EMAIL PROTECTED] Now, the following happens when I try to do it [EMAIL PROTECTED]:~/public_html$ rlogin node01 Password: Login incorrect login: rlogin: connection closed. [EMAIL PROTECTED]:~/public_html$ rsh node01 Password: Login incorrect login: rlogin: connection closed. [EMAIL PROTECTED]:~/public_html$ The authentication log on node01 (/var/log/auth.log) is as follows: Nov 18 17:49:09 node01 pam_rhosts_auth[9285]: allowed to [EMAIL PROTECTED] as exa Nov 18 17:49:09 node01 in.rlogind[9285]: PAM authentication failed for in.rlogind Nov 18 17:49:10 node01 PAM_unix[9286]: check pass; user unknown Nov 18 17:49:10 node01 PAM_unix[9286]: authentication failure; (uid=0) -> exa for login service Nov 18 17:49:13 node01 login[9286]: FAILED LOGIN (1) on `pts/1' from `borg' FOR `exa', Authentication service cannot retrieve authentication info. Nov 18 17:49:18 node01 pam_rhosts_auth[9287]: allowed to [EMAIL PROTECTED] as exa Nov 18 17:49:18 node01 in.rlogind[9287]: PAM authentication failed for in.rlogind Nov 18 17:49:19 node01 PAM_unix[9288]: check pass; user unknown Nov 18 17:49:19 node01 PAM_unix[9288]: authentication failure; (uid=0) -> exa for login service Nov 18 17:49:22 node01 login[9288]: FAILED LOGIN (1) on `pts/1' from `borg' FOR `exa', Authentication service cannot retrieve authentication info. What the heck is this supposed to mean? I'd really like to remove this PAM thing from my cluster :( Thanks, -- Eray (exa) Ozkural Comp. Sci. Dept., Bilkent University, Ankara e-mail: [EMAIL PROTECTED] www: http://www.cs.bilkent.edu.tr/~erayo
