Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtune!akguc!akgua!gatech!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP
Newsgroups: net.unix
Subject: Re: sh, csh, and special execution environments
Message-ID: <2026@umcp-cs.UUCP>
Date: Sun, 15-Jun-86 17:37:04 EDT
Article-I.D.: umcp-cs.2026
Posted: Sun Jun 15 17:37:04 1986
Date-Received: Tue, 17-Jun-86 11:08:38 EDT
References: <931@uwvax.UUCP> <1913@osu-eddie.UUCP>
Reply-To: chris@maryland.UUCP (Chris Torek)
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 23

In article <1741@utah-gr.UUCP> thomas@utah-gr.UUCP (Spencer W. Thomas) writes:
>You missed.  Since when does rsh use sh?

I am afraid that you missed too, Spence.  It uses `sh' if the remote
user's login shell is `sh'.  Rare perhaps, but by no means unheard-of.

>The problem that pfeiffer was complaining about has to do with
>quoting variable expansions so that they occur properly whether the
>command is being run remotely or locally.

This is probably true.

>You have to supply an extra level of quoting for remote commands
>(to deal with remote file expansion &c).  This is especially nasty
>if you have `!'s in your string somewhere.

The quoting is not too terribly hard to do.  Perhaps there should
be a utility called `quote' that quotes its arguments against shell
expansion :-).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu