🚀 go-pugleaf

I get this result both on Sun 3's running SunOS 3.5 and Sun 4's
running SunOS 4.0.1.

When executed via an rsh command, bash runs .profile as well as
.bashrc.  I am not even able to generate a script of this because the
rsh does not then terminate correctly.  I cut the following out of an
xterm window:  (phoenix and tartarus are both Sun 4's.) 

phoenix >> rsh tartarus cat /dev/null
starting .profile
stty: Operation not supported on socket
starting .bashrc
stty: Operation not supported on socket
default
[: too many arguments
not a tty
Wed Oct 25 10:56:15 CDT 1989
starting .bashrc
starting .bashrc
Expunging files deleted two days ago or more.
<19358>
nitie nite!
<19359>
^Z
[1]+  Stopped             rsh tartarus cat /dev/null
phoenix >> kill %1

[1]+  Stopped (tty input) rsh tartarus cat /dev/null
phoenix >> fg
rsh tartarus cat /dev/null
phoenix >>


The "starting .foo" commands I inserted in the respective files for
illustration purposes.  My .profile sets up a .logout file to be
executed on termination of the shell.  Everything after the date is
the normal behaviour of that script.

I backed out the change I sent earlier (on handling binary files) and
I still get the same results.  This does NOT happen with bash 1.02 on
any of our machines.

				     -- La Monte H. Yarroll
			Preferred:	piggy@gargoyle.uchicago.edu