Re: Cygwin shells exit immediately

2004-03-18 Thread Aaron Humphrey
Igor Pechtchanski wrote: > Did you try running bash non-interactively with a long-running command, > e.g., 'bash -c "sleep 20"'? Does that work? It doesn't return an error, but it doesn't take any more or less time to return than bash -c "sleep 1" or bash -c "sleep 150" > Does 'bash --norc -i

Re: Cygwin shells exit immediately

2004-03-18 Thread Igor Pechtchanski
On Thu, 18 Mar 2004, Aaron Humphrey wrote: > 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. > > Anoth

RE: Cygwin shells exit immediately

2004-03-18 Thread Buchbinder, Barry (NIH/NIAID)
See the thread starting with http://sources.redhat.com/ml/cygwin/2004-03/msg00811.html -Original Message- From: Aaron Humphrey [mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004 2:18 PM To: [EMAIL PROTECTED] Subject: Re: Cygwin shells exit immediately Further (mostly negative

Re: Cygwin shells exit immediately

2004-03-18 Thread Aaron Humphrey
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,