Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: jorg DOT schaible AT db DOT com X-Lotus-FromDomain: DMG UK AT DEUBAINT To: cygwin AT sourceware DOT cygnus DOT com Message-ID: <412568E0.007C3475.00@dbogw2-e1.esb.eur.deuba.com> Date: Mon, 15 May 2000 22:36:37 +0000 Subject: Re: Slow startup of all cygwin tools. Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Cygwin V1.x mounts the root in binmode. Convert your .bashrc (and .inputrc) to UNIX format with LF line endings only. ---------------------------------------- Message History ---------------------------------------- From: alan DOT conway AT iona DOT com on 15/05/2000 19:54 To: cygwin AT sourceware DOT cygnus DOT com cc: Subject: Slow startup of all cygwin tools. I've just installed cygwin 1.1.0 and there is a very long delay (about 30-40 secs) on startup of any of the tools when run from a CMD shell. This did not happen with the B20 release. Any idea why this might be? Running tools inside of bash is fine, so it looks like something that happens while loading cygwin.dll - but what is the DLL doing that takes so much time? Is there some network madness in the DLL initialisation? Help much appreciated, this is causing me much grief. Cheers, Alan. -- Alan Conway, Engineer, IONA Technologies. E-mail: alan DOT conway AT iona DOT com Tel: +1(819)847-1878 Fax: +1(819)847-0255 Snail-mail: 660 Genest, Magog, QC, J1X 4Y7, Canada. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com