Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: No longer works.Igor Pechtchanski <pechtcha AT http://cygwin.com/acronyms#PCYMTNQREAIYR>
Date: Tue, 5 Oct 2004 10:35:10 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <200410051126.18477.d_baron@012.net.il>
Message-ID: <NUTMEGmRBtyiUDYuC8H00000267@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 05 Oct 2004 09:35:10.0829 (UTC) FILETIME=[9BD719D0:01C4AABE]

> -----Original Message-----
> From: cygwin-owner On Behalf Of David Baron
> Sent: 05 October 2004 10:26

> This was the exact thing that happened to another poster on 
> the same digest. 
> The batch file containing a cd the ..\cygwin\bin and a bash 
> -i -login simply 
> flashes closing immediately.


  Which means that something, probably bash itself, is failing very early, and the
shell closes after the bat file exits.

  In circumstances like these it can be very informative to open a normal dos
shell, cd into the cygwin root dir, and manually enter the commands from the .bat
file to see which one fails and in what way.



    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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