Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ritcv.UUCP
Path: utzoo!linus!vaxine!wjh12!genrad!grkermit!masscomp!clyde!floyd!harpo!seismo!rochester!ritcv!kar
From: kar@ritcv.UUCP
Newsgroups: net.bugs.4bsd
Subject: Re: rsh eats # character
Message-ID: <995@ritcv.UUCP>
Date: Wed, 11-Apr-84 18:38:12 EST
Article-I.D.: ritcv.995
Posted: Wed Apr 11 18:38:12 1984
Date-Received: Fri, 13-Apr-84 01:51:56 EST
References: <1510@vax4.fluke.UUCP> <3330@brl-vgr.ARPA>
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 10

This occurs when your shell on the remote machine is csh.  The reason it occurs
is that csh is invoked with the -c option to process a single command.  In
this mode, it does not think it is "interactive" (e.g. it does not read .login,
it thinks # begins a comment) and so behaves differently than when you really
log in to the remote machine and type the command in by hand.  The fix to this
is not in rsh but in csh, so that the -c option looks at the command in the
same way an interactive shell would.

	Ken Reek, Rochester Institute of Technology
	{allegra,seismo}!rochester!ritcv!kar