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
From: Sam Edge <sam DOT edgeZZZ AT lineone DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin.bat
Date: Sun, 11 May 2003 04:15:05 +0100
Organization: .
Reply-To: cygwin AT cygwin DOT com
Message-ID: <cberbvchj7spile99755mhhikb02226t1f@4ax.com>
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0305092330000 DOT 9872-100000 AT slinky DOT cs DOT nyu DOT edu> <3EBC77C9 DOT 7090605 AT m8y DOT org> <3EBC793B DOT 9000301 AT rfk DOT com> <cslqbvgnnuvlpbd5fccejfru9ranq49svv AT 4ax DOT com> <20030511002234 DOT GD17951 AT redhat DOT com> <urbrbv4vqmvrba6j71v5qfhderlgig8g53 AT 4ax DOT com> <20030511021835 DOT GB18826 AT redhat DOT com>
In-Reply-To: <20030511021835.GB18826@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Posting-Agent: Hamster/2.0.0.1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h4B3FVF24990

cgf wrote in <20030511021835 DOT GB18826 AT redhat DOT com>
in gmane.os.cygwin on Sat, 10 May 2003 22:18:35 -0400:

> >> >If you use cygwin.bat, then under Windows NT/2k/XP you first have a
> >> >CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
> >> >doing nothing until the bash.exe process exits.
> >> > [snip]

> >Negligible on a modern PC. Noticeable on some of the kit I've got
> >here. ;-)

> I *really* find that hard to believe.  I've run cygwin on some pretty
> slow computers and I've never noticed a slowdown from running bash
> in a command shell.  Even Windows should be smart enough to know that
> it can swap out most of command.com when bash.exe is running so I
> don't know how this could be a resource thing.

Oh yes. I've already said that the general system slow down due to one
extra waiting process isn't going to be noticeable. (Although just
because a process is swapped out doesn't mean it ceases consuming
resources, especially on Windows!)

But the overhead in /launching/ an extra CMD.EXE to process the ".BAT"
file that then starts up bash.exe can be noticed on old kit under NT.

I suspect that on Win9x the difference is much smaller because,
whether I start bash.exe directly or via cygwin.bat, a WINOA386.MOD
process is always created as well as a BASH.EXE.

-- 
Sam Edge

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