Hi folks,

I'm in the process of setting up a (test) Beowulf cluster. One of the things I need to be able to do (and I have more explanation of why I want to do some of the seemingly dumb things here) is allow my users to rsh between nodes. I have so far apparently managed reasonable firewall settings and settings for hosts.deny and hosts.allow so that the only thing users from outside the cluster can do is ssh, but my users on the real cluster have lots of scripts that use rsh, and within the private network of that cluster it's not a security problem, so I don't want to force them to use ssh with its additional overhead there.

I can now ssh from node to node within the test cluster also, but when I do, I get this oddity that I've never seen before. Here's an example

So, what is the "default context" and why is rlogin causing me to need to answer a question about it here. If I do what seems like it should be the "same thing" on the production cluster I get this:

I googled for:
linux rlogin "default context"
and found nothing that I could identify as useful. Does anyone have suggestions for better search terms?

What is this "default context"? Does anyone recognize this phenomenon? If so, does anyone have any suggestions for me? I really don't want users to have to answer a question like this every time they rlogin because my users are going to need to rsh a lot. The "real" cluster is currently running RH 8.0 and the test cluster is running RHEL4, so I can prepare for the OS upgrade to the real one.

Thanks,
Paul

Moved at users request.

I found that changing the line

session required pam_selinux.so multiple open

in /etc/pam.d/login and /etc/pam.d/remote

To remove the reference to multiple

i.e.


session required pam_selinux.so open