X-Spam-Check-By: sourceware.org Message-ID: <4e41f5c20703201645j4af40c09l631d99f44a0e2baf@mail.gmail.com> Date: Tue, 20 Mar 2007 17:45:13 -0600 From: "Morgan Gangwere" <0 DOT fractalus AT gmail DOT com> To: cygwin AT cygwin DOT com Subject: Re: slow bash spawn In-Reply-To: <03c801c76afd$96e775d0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <02a201c76963$f26a73d0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <03c801c76afd$96e775d0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com well, I have this problem too occasionally. normally caused if its an SP2 machine. never have this problem on sp1 or noSP. also, if I disable the DLA sysyem, i cant access flash disks. another thing to think about is, what does bash do with $0 or ARGV[0] ? if it sees its "bash" then its gonna act differently than if its "sh." just a thought... On 3/20/07, Dave Korn wrote: > On 20 March 2007 08:17, Marc Compere wrote: > > > Well, it seems I've found the problem, or at least a big component of > > the problem. Turns out it is likely not (directly) related to cygwin > > code but some other interaction between cygwin and the OS as a result of > > a Sonic Solutions DLA process running. DLA apparantly stands for Drive > > Letter Access Component. Exact process name is > > c:\windows\system32\dla\dlactrlw.exe. Snapshot attached. > > > > Being fed up with long XP boot-up times I had downloaded Autoruns and > > removed many, seemingly unnecessary startup processes and services. > > Oops, apparantly dlactrlw.exe is necessary for Cygwin to run quickly as > > usual. Never would have guessed - still don't quite understand how a > > Sonic cd burner software (I presume) causes the slow down, but it's > > pretty repeatable. 5 reboots later there's a 1-to-1 correspondence with > > this process and fast cygwin bash-related commands, including > > ./configure and make. > > > > bash --login -i -x takes 33 seconds with DLA turned off (via Autoruns > > checkbox) and takes about 5.5 seconds with this process turned on. Go > > figure? > > > That's most likely the difference between merely disabling one component of > an application, leaving the remaining ones installed and broken, and properly > uninstalling it. Perhaps something that hooks into every process in the > system is calling out to the DLA component and waiting for a timeout before it > fails. > > I'll add DLA to the theoretical cygwin-list-of-dodgy-apps. > > cheers, > DaveK > -- > Can't think of a witty .sigline today.... > > > -- > 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/ > > -- Morgan gangwere "Space does not reflect society, it expresses it." -- Castells, M., Space of Flows, Space of Places: Materials for a Theory of Urbanism in the Information Age, in The Cybercities Reader, S. Graham, Editor. 2004, Routledge: London. p. 82-93. -- 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/