Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <200003311625.KAA04456@hp2.xraylith.wisc.edu>
To: earnie_boyd AT yahoo DOT com
cc: Mo DeJong <mdejong AT cygnus DOT com>,
        cygwin developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: Mo Dejong's install problems 
In-reply-to: Your message of "Fri, 31 Mar 2000 07:44:09 PST."
             <20000331154409 DOT 9248 DOT qmail AT web110 DOT yahoomail DOT com> 
Date: Fri, 31 Mar 2000 10:25:04 -0600
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>

Earnie Boyd <earnie_boyd AT yahoo DOT com> writes:
> 
> Well, since you brought up using the DOS Command process as the "shell", here
> is another brainstorm of mine.  Have a stub process that keeps the Cygwin dll
> initialized.  This would have to be user configurable, SET CYGWIN=...
> [no]keepalive ..., with a default of nokeepalive.  This would help speed the
> processes when using the DOS Command shell.

A long time ago, I added Cygwin dll to the "Known DLLs" list, but I don't
remember if I saw any significant improvements. 

For those not familiar with Known DLLs list, a registry key in windows
contains a list of DLLs that windows knows about, and it optimizes the
loading process. The downside is that WIndows will always load the same
one, even if you have multiple DLLs with the same name, and say you want
to load a different one for testing. 

One way is to create a tiny Cygwin app that is always running, and that
creates that shareable area that all Cygwin processes attach to. Sort of
a 'init' process. If it's dead, the next Cygwin DLL load will start it
again.

Don't know if that will improve the performance however. Needs some
profiling.

Regards,
Mumit