unable to rlogin/rsh is shell is non-standard (bash/tcsh)

[Patrick Hawley]

Hello. Most of our users are Linux folks, and therefore have become quite comfortable with bash (and tcsh). So I installed bash (2.04) and tcsh on our 9000 (which is running HP-UX 11.0).

However, if a user who has his/her shell set to bash/tcsh attempts to rlogin, it hangs and I have to kill that PID for bash/tcsh. But if I set the user's shell to /sbin/sh, he/she can rlogin without issue, plus can then run /bin/bash after having logged on.

I know I'm missing something basic here, but not even having slept on it last night produced any insight.

Background:
I downloaded the binaries of bash/tcsh from hpux.cs.utah.edu. Initially, I'd simply set up sym links to the installed binaries (/opt/bash/bin/bash) from /bin, after which I've tried copying the binary to /bin, plus I've set the permissions/ownership just as they are for /sbin/sh.

Any help would be greatly appreciated.

[Vincenzo Restuccia]

See http://www.dutchworks.nl/htbin/hpsysadmin?h=3&dn=50272&q=unable%20to%20rlogin%2frsh%20is%20shell%20is%20non-standard%20%28bash%2ftcsh%29&fh

[James R. Ferguson]

Hi Patrick:

Add the shell name (e.g. /usr/bin/bash) to /etc/shells. If you do not have /etc/shells, then create one with the stand shells plus the ones you want to allow. It should look something like:

#...Standard Shells...
#
/sbin/sh
/usr/bin/sh
/usr/bin/rsh
/usr/bin/ksh
/usr/bin/rksh
/usr/bin/csh
/usr/bin/keysh
#
#...Non_Standard Shells...
#
/usr/bin/tcsh
/usr/bin/bash
#_end

See 'man 4 shells'.

Also: /bin is an old transition (link) directory. It points to /usr/bin by default, but you should reference /usr/bin so that when the day finally comes...

Regards!

...JRF...

[Patrick Hawley]

Vincenzo and James, thanks for the lonk, but my /etc/shells and /etc/inetd.sec are both in order.

Also, I *am* able to rlogin if I set my shell to /sbin/sh.

Thanks again!

[Patrick Hawley]

Well, I was able to fix bash by building it from source, though having done the same for tcsh, I am confronted with the same problem, hanging at rlogin, though one can run the shell after successfully logging in.

It doesn't really seem like an HP-UX problem, though I'd originally hoped that someone would come along and say "I had the same problem, and you know what fixed it? ....", but alas.

Thanks though, as always, for all of your help on this issue, and so many others that save me from having post more often than not! These forums are a _true_ knowledge base!

Patrick