X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<47A0C1C1.7070505@cygwin.com>
Date:	Wed, 30 Jan 2008 13:28:17 -0500
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070505 Remi/2.0.0.0-3.fc4.remi Thunderbird/2.0.0.0 Mnenhy/0.7.5.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: bash's builtin "test" command kills bash on Windows Server 2003 R2
References:	<47A0B606 DOT 2070408 AT sgi DOT com>
In-Reply-To:	<47A0B606.2070408@sgi.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Brian J. Johnson wrote:
> I've encountered an odd problem installing cygwin on Windows Server 2003 
> R2, Enterprise x64 edition.  This is a default installation of cygwin 
> from yesterday on a fresh Windows installation on a Xen VM hosted by 
> SLES10SP1.
> 
> The installer runs normally, but most of the postinstall scripts fail. I 
> eventually traced the problem to a failure with bash's builtin "test" 
> and "[" commands.
> 
> If I run a basic "test" command like this:
> 
>   $ test -e /
> 
> then the shell simply exits, without printing any error messages.  There 
> are no errors reported in the Windows error log.  If I try this:
> 
>   $ test -e / ; echo hi
> 
> then the shell exits without echoing, and without printing any error 
> messages.  If I use the external test command:
> 
>   $ /bin/test -e / ; echo hi
> 
> then "hi" is echoed as expected.  This happens with almost all arguments 
>  to "test" that I've tried... even "test 1" kills the shell in the same 
> way.  However, just "test" with no arguments doesn't trigger the problem.
> 
> Cygwin1.dll and bash from various time periods fail in the same way. 
> Cygwin versions which work on other machines with other versions of 
> Windows fail on this machine.  So it appears to be an issue with this 
> particular Windows installation.
> 
> Any suggestions on what to try?  I see from the mailing list that others 
> have cygwin working on Windows Server 2003 64-bit.
> 
> Cygcheck output is below.  Strace output available on request.  (Note 
> that cygcheck shows Microsoft's SUA is installed.  It failed the same 
> way before and after I installed SUA.)
> 
> Thanks,

What does 'type -a test' say?  Are you sure you're not getting something
from SUA?

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

- Raw text -