Message-ID: <45BD02B4.6090907@huarp.harvard.edu>
Date: Sun, 28 Jan 2007 15:08:20 -0500
From: Norton Allen <allen@huarp.harvard.edu>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: cygwin list <cygwin@cygwin.com>
Subject: Re: bug with built-in commands in bash when redirecting output
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (ent.arp.harvard.edu: 24.61.82.50 is authenticated by a trusted mechanism)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

>
>
>The following one liner illustrates a bug in sh:
>$ /bin/bash -c '/bin/bash -cx '\''x=`echo hello`'\''' > @x
>++ echo hello
>+ x=$'hello\r'
>$
>  
>
I'm wondering if the problem I am seeing is from the same source. I find 
that 'apachectl stop' no longer works since a recent cygwin update. I 
can see that the PIDFILE is being written with a \r\n line ending. 
'apachectl stop' then reads the file with

    PID=`cat $PIDFILE`

$PID then includes the \r character, and the subsequent kill operation 
fails as a result.

Is there something that changed recently that is causing this to fail 
now? I'm pretty sure this worked until recently.

Norton Allen


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