From:	gwatts AT fnal DOT gov (Gordon Watts Brown University)
Subject:	Long startup times in b19
7 Mar 1998 16:47:19 -0800 :
Message-ID:	<01IUAZLN3HEC0000AJ.cygnus.gnu-win32@FNAL.FNAL.GOV>
Mime-Version:	1.0
To:	gnu-win cygnus mailing list <gnu-win32 AT cygnus DOT com>

Hi,
  I, too, am observing very long startup times for bash. I spent a little
time characterizing them.

- bash shell startup takes on the order of 20 or 30 seconds.
- running mount from the command line takes 20 or 30 seconds.
- if another bash shell is already running, startup is less than one second,
as does the mount from DOS.
	Looks like the time is spent in the dll startup code??
- startup time is not affected if I remove all my mount points from the
registry
- startup time is not affected if I remove my .bashrc files
- I do not have a local hosts file (a previous email referred to this): who
just fails right away when I run it.
- I set my PATH variable to include only the bin area of the b19
distribution (it contains a lot of over-the-net entries), and that did not
have an effect.
- CPU time is almost zero during this time. No page faults either. Looking
with the performance monitor does not indicates kernel cpu time is less than
5% (so I doubt it is trying to relocated the dll or something like that).

  I figure something is busted in my configuration, so it is only a matter
of figureing out what!

  From here I'm stuck; the next logical thing is to attempt to debug this
thing... Where is a good place to start?

  BTW, once a single bash shell is started, then things go very quickly.

	Cheers,
		Gordon.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -