Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rutgers!mcnc!ecsvax.uncecs.edu!dukeac!wolves!ggw
From: ggw@wolves.uucp (Gregory G. Woodbury)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: rsh vs remsh -- how does one handle the name conflict?
Summary: shell functions
Message-ID: <1990Feb3.061647.12806@wolves.uucp>
Date: 3 Feb 90 06:16:47 GMT
References: <11004@encore.Encore.COM>
Reply-To: ggw@wolves.UUCP (Gregory G. Woodbury)
Followup-To: comp.protocols.tcp-ip
Organization: Wolves Den UNIX BBS
Lines: 38

DOUG@YSUB.BITNET ("Doug Sewell"):
- On our Encore (4.2-based) system, there is no '/bin/rsh'.  If I enter
- 'rsh' on the Encore, it wants to know what host to use.
- 
- So, I'd conclude rsh (remote shell) is a Berkeleyism, and rsh (restricted
- shell) is a ATTism.

	At work, on the Opus 88k's and Clippers, /bin/rsh is the restricted
shell and /usr/bin/rsh is the remote shell (sometimes in /usr/ucb/rsh). They
recommend renaming it to rmtsh if you want to and note that in a homeogenous
environment it should not create a problem.

	Personally, I define a (bourne) shell function "rsh" that references
the /usr/bin/rsh program and passes all the arguments to that.  Also, in the
small network we have, I define shell functions that are the names of the other
machines in the dept that invoke rsh with at fixed first argument and passing
the rest of the args to the machine bing sought.

The functions look like:
	rsh(){
		/usr/bin/rsh $@
	}

	aliceb(){
		if [ $# -eq 0 ]
		then
			rlogin aliceb
		else
			rsh aliceb TZ=EST5EDT $@
		fi
	}
-- 
Gregory G. Woodbury
Sysop/owner Wolves Den UNIX BBS, Durham NC
UUCP: ...dukcds!wolves!ggw   ...dukeac!wolves!ggw           [use the maps!]
Domain: ggw@cds.duke.edu  ggw@ac.duke.edu  ggw%wolves@ac.duke.edu
Phone: +1 919 493 1998 (Home)  +1 919 684 6126 (Work)
[The line eater is a boojum snark! ]           <standard disclaimers apply>