From muir@idiom.com  Sat Jan 14 05:14:50 1995
Received: from idiom.com (idiom.com [140.174.82.4]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id FAA02884 for <FreeBSD-gnats-submit@freebsd.org>; Sat, 14 Jan 1995 05:14:46 -0800
Received: (from muir@localhost) by idiom.com (8.6.9/8.6.9) id FAA24921; Sat, 14 Jan 1995 05:14:44 -0800
Message-Id: <199501141314.FAA24921@idiom.com>
Date: Sat, 14 Jan 1995 05:14:44 -0800
From: David Muir Sharnoff <muir@idiom.com>
Reply-To: muir@idiom.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: The -e flag of rlogin is not supported by rsh.
X-Send-Pr-Version: 3.2

>Number:         136
>Category:       bin
>Synopsis:       The -e flag of rlogin is not supported by rsh.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan 14 05:20:01 1995
>Closed-Date:    Sat Jan 14 12:36:30 PST 1995
>Last-Modified:
>Originator:     David Muir Sharnoff
>Release:        FreeBSD 2.0-RELEASE i386
>Organization:
Idiom Consulting
>Environment:

>Description:

	Since time immortal (at least since 4.3 days), rsh has been able
	to handle exec'ing an rlogin.  You could always replace 'rlogin'
	with 'rsh' and nothing would break.  This includes -e flag.

	rlogin supports the -e<CHAR> flag.

	rsh will allow -e, but not -e<CHAR>.  

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: wollman 
State-Changed-When: Sat Jan 14 12:36:30 PST 1995 
State-Changed-Why:  
Fixed in rev 1.3 of rsh.c. 
>Unformatted:



