Solaris 2.6+ <rsh cmd> doesn't source .bashrc

[brett]

Configuration Information [Automatically generated, do not change]:
Machine: sparc
OS: SunOS5
Compiler: gcc
Compilation CFLAGS:   -DHAVE_VFPRINTF -DHAVE_UNISTD_H -DHAVE_STDLIB_H 
-DHAVE_LIMITS_H -DHAVE_GETGROUPS -DHAVE_RESOURCE -DHAVE_SYS_PARAM 
-DVOID_SIGHANDLER -DUSGr4 -DUSG -DSolaris -DOPENDIR_NOT_ROBUST -DNO_SBRK_DECL 
-DINT_GROUPS_ARRAY -DHAVE_WAIT_H  -DHAVE_DUP2 -DHAVE_STRERROR  -DHAVE_DIRENT_H 
-DHAVE_STRING_H -DHAVE_VARARGS_H -DHAVE_STRCHR  -DHAVE_DEV_FD -Dsparc -DSunOS5 
-DSHELL -DHAVE_ALLOCA -DHAVE_ALLOCA_H  -O
uname output: SunOS penguins 5.5.1 Generic_105428-01 sun4u sparc SUNW,Ultra-5_10

Bash Version: 1.14
Patch Level: 5

Description:
        I have a user who has /usr/local/bin/bash (compiled on a
        Solaris 2.4 machine) as his login shell.  He has been using it
        successfully to remotely execute single commands, as in "rsh
        validate," on Solaris 2.5 machines.  However, on Solaris 2.6
        or above, using rsh in this fashion doesn't source his .bashrc
        file, so his PATH isn't set up correctly.  When using rlogin,
        or rsh as rlogin, .bashrc is sourced, and everything is fine.
        He also has no problem rsh'ing to Solaris 2.6 machines which
        have bash version 2.04 installed.  I browsed through the
        changelog, and found brief references to "improved" detection
        of rsh on Solaris.  Is this the problem I am seeing?  Will
        upgrading to 2.04 or above fix the problem?  Should I instead
        recompile bash 1.14.5 for Solaris 2.6?

Repeat-By:
        Place "echo at top" at the top of .bashrc
        Use bash as your login shell
        % rsh solaris-2.6-host echo junk
        Observe that "at top" is not printed.