Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: RSH1001 rsh command error Date: Wed, 21 Jan 2004 12:51:04 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <5.1.1.1.2.20040121130905.022a8d68@mail.madrid.eur.slb.com> Message-ID: X-OriginalArrivalTime: 21 Jan 2004 12:51:04.0492 (UTC) FILETIME=[3AFE3EC0:01C3E01D] > -----Original Message----- > From: cygwin-owner On Behalf Of Alberto Serrano de la Casa > When I try the command : > > rsh ls > > I get next error: > > RSH1001: The Local user name is undefined; it is not in the > registry and it is not defined as the NETUSER environment variable. > > However, If I execute > > rsh -l ls > > It works! > > I don't undesrtand at all , because the values of USER and > USERNAME values are the same as . > > Any help, please? 1) This isn't a cygwin problem. 2) The error message makes it perfectly clear that RSH expects an environment variable called NETUSER, not USER or USERNAME. 3) It's still not a cygwin problem. 4) Although when you're using rsh the username on the remote system is usually the same as your local username, sometimes you'll want to act as a different user on the remote system. That's why rsh uses a different variable rather than USER or USERNAME. 5) It's still not a cygwin problem. 6) Did you read the man page for rsh "man rsh", the info page "info rsh", or the usage info "rsh --help" before you posted this? 7) It's still *soooooo* not a cygwin problem. The cygwin version of rsh doesn't even contain the text for that error message you just described. Are you using MKS or SFU rsh, perhaps? DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/