www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/03/18/14:15:22

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id: <s059937d.031@KAKARI.KAKARI.COM>
Date: Thu, 18 Mar 2004 12:17:51 -0700
From: "Aaron Humphrey" <HumphreyA AT Kakari DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Re: Cygwin shells exit immediately
Mime-Version: 1.0
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i2IJFGBV003763

Further (mostly negative) information on the problem:

Nothing shows up in the Windows System Log when bash exits.

Bash stays open to type maybe half a dozen characters, and can run, say, "ls"
before exiting.

A reboot didn't help.

Another person on the same network has no problems with Cygwin, though he
hasn't ugpraded to 1.5.8-1 yet.

I noticed that in the cygcheck output I sent, all the DLLs seemed to show up
twice, but that may just be because I ran it from C:\Cygwin\bin.


--Aaron V. Humphrey
Kakari Systems Ltd.



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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019