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: <1065941935.3f88fbaf13501@pandani.services.adelaide.edu.au>
Date: Sun, 12 Oct 2003 16:28:55 +0930
From: Milton Woods <milton DOT woods AT adelaide DOT edu DOT au>
To: cygwin AT cygwin DOT com
Subject: Re: Pause after Calling ExitProcess
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 129.127.248.111

> I have found that some external programs invoked from a shell take a 
> long time to return control to the shell on exit. For example, typing
> 'hostname<enter>' at the command prompt displays a response within about
> 1 second, but the prompt does not appear for another 3 seconds (on a 
> 1.6GHz P4).

The problem was caused by the Novell client (version 4.5). Upgrading to the
latest version (4.9) made Cygwin much more responsive.

Milton Woods.

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