Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <40328A2E.80900@acm.org>
Date: Tue, 17 Feb 2004 13:39:58 -0800
From: David Rothenberger <daveroth@acm.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: 2004-Feb-17 snapshot change ssh option parsing behavior
References: <16434.32879.365152.633519@forbin.entomo.com> <20040217212425.GB18953@cygbert.vinschen.de>
In-Reply-To: <20040217212425.GB18953@cygbert.vinschen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com

Corinna Vinschen wrote:
> On Feb 17 12:58, David Rothenberger wrote:
> We're using the latest plain BSD getopt() now.  It's permuting the
> options by default.  This was switched off by default in Cygwin so far.
> 
> Typically you should quote the command you send to the remote host:
> 
>   ssh somehost '/bin/bash --login -c date'

Yeah, that's an easy fix for this simple case, but I have a bunch of other 
scripts that have quotes in the command sent to ssh, which makes adding 
another level of quotes "fun."

> Another way to accomplish what you want is to set the environment
> variable POSIXLY_CORRECT prior to calling ssh.

That's helpful.  Thanks.

This change broke a number of my scripts.  I wonder how many other similar 
error reports will be made by other users when 1.5.8 is released?

Dave


--
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/

