Mail Archives: cygwin/2003/11/13/02:32:44
Thanks to all who replied - Brian, Reid, Eric Rolf, kevin, shankar ; Sorry
if I have left out any, I'm glad to say that I was able to find out why and
that solved my problem. It was with the HOME variable which was by default
set to /cygwindrive/h or something like that. Being a total newbie on
Windows, I did not bother to touch this. Not I have learnt how to set
environment variables in Windows and have set it to c:\ and the problem I
was seeing disappeared. I promise to read the FAQ/Documentation do some
googling etc :)
Thanks again !
Koundinya
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
Of Shankar Unni
Sent: Wednesday, November 12, 2003 11:52 PM
To: cygwin AT cygwin DOT com
Subject: Re: cygwin too slow
koorapati, koundinya wrote:
> In strace I'm not able to see
> which system call is eating up so much time as when I start a program say
> 'ls' with strace, I see nothing and only as ls begins to run after getting
> loaded, strace throws it's output.
He's sort of right in that often, there's a mysterious wait of a second
or two, even on a completely unloaded system, before the process starts
running.
I suspect it has something to do with our flaky network (we're in a
workgroup without a primary WINS server or a domain controller). Even if
there are no network drives in the path, I suspect that things like
looking up the local host name will also be slow if there are subtle
network problems like this, and can cause this delay on startup..
--
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/
--
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/
- Raw text -