> IP> (...) this is not a Cygwin problem at all. (...)
>
> Thank you Igor,
> you were very helpful, indeed.
> Of course, this was not a cygwin problem,
> and narrowing it down to the cygwin_gethostname call
> directed me to some old thread:
> http://www.cygwin.com/ml/cygwin/2003-03/msg00097.html
IP> (...) this is not a Cygwin problem at all. (...)
Thank you Igor,
you were very helpful, indeed.
Of course, this was not a cygwin problem,
and narrowing it down to the cygwin_gethostname call
directed me to some old thread:
http://www.cygwin.com/ml/cygwin/2003-03/msg00097.html
(I was not alone
On Tue, 27 Jan 2004, pd wrote:
> Tuesday, January 27, 2004, 9:09:36 PM, you wrote:
>
> IP> Now you 'strace' both calls to see where the time goes (each gives about
> IP> 300 lines of strace and, FWIW, each takes <.2s on my Win2k machine).
>
> In both cases (uname and hostname) the problem is with
Tuesday, January 27, 2004, 9:09:36 PM, you wrote:
IP> Now you 'strace' both calls to see where the time goes (each gives about
IP> 300 lines of strace and, FWIW, each takes <.2s on my Win2k machine).
In both cases (uname and hostname) the problem is with
cygwin_gethostname: name 103baran
Almost
On Tue, 27 Jan 2004, pd wrote:
> yes, I noticed two strange things:
> time hostname
> and
> time uname -s
> are giving me circa 3.54 secs each!
>
> but now what?
>
strace them to see what call is taking all the time.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Syste
On Tue, 27 Jan 2004, pd wrote:
> Tuesday, January 27, 2004, 8:42:47 PM, you wrote:
>
> IP> Ugh, I caught the typo on my command line, but forgot to change the
> IP> message. Make that "bash --login -i -x -c true". Sorry.
> IP> Igor
> yes, I noticed two strange things:
> time hostname
> and
>
Tuesday, January 27, 2004, 8:42:47 PM, you wrote:
IP> Ugh, I caught the typo on my command line, but forgot to change the
IP> message. Make that "bash --login -i -x -c true". Sorry.
IP> Igor
yes, I noticed two strange things:
time hostname
and
time uname -s
are giving me circa 3.54 secs each
On Tue, 27 Jan 2004, Igor Pechtchanski wrote:
> On Tue, 27 Jan 2004, pd wrote:
>
> > Hello,
> > 9 seconds to start up bash on PIV 2.6 machine is way too slow
> > for me :-)
>
> Hear, hear.
>
> > The faq q&a "Why is Cygwin suddenly so slow?" probably doesn't
> > fit here, because I had never have c
On Tue, 27 Jan 2004, pd wrote:
> Hello,
> 9 seconds to start up bash on PIV 2.6 machine is way too slow
> for me :-)
Hear, hear.
> The faq q&a "Why is Cygwin suddenly so slow?" probably doesn't
> fit here, because I had never have cygwin 1.3.3 or earlier on my
> machine.
Yes, you don't seem to
Hello,
9 seconds to start up bash on PIV 2.6 machine is way too slow
for me :-)
The faq q&a "Why is Cygwin suddenly so slow?" probably doesn't
fit here, because I had never have cygwin 1.3.3 or earlier on my
machine.
Please help with any suggestions.
Pawel
output from cygcheck -s -v -r follows:
10 matches
Mail list logo
