On 10 October 2006 21:06, Peter Jay Salzman wrote:
> There appears to be a stochastic delay in the "ls" program. I used bash's
> time function to time how long it takes for ls to do its job (output of "ls"
> suppressed):
>
> real m10.492s user 0m0.030s sys 0m0.030s
> real m 0.074s user 0m0.030s sys 0m0.062s
> real m 0.075s user 0m0.046s sys 0m0.030s
> real m 8.641s user 0m0.046s sys 0m0.015s
> real m 0.072s user 0m0.030s sys 0m0.046s
> real m 0.072s user 0m0.030s sys 0m0.046s
> real m 0.074s user 0m0.046s sys 0m0.046s
> real m 0.077s user 0m0.045s sys 0m0.046s
> real m10.854s user 0m0.030s sys 0m0.046s
>
> I'm attaching cygcheck output and an strace of ls.
YOW!!! CR-CR-LF lineendings! :-) Are you trying to start a fight, or what?
> Any help of reducing or eliminating this delay would be greatly appreciated.
Well, it's quite likely that something else in your system is interfering
and locking it out, but I do wonder:
c:\Program Files\QuickTime\QTSystem\
\\fitch.corp\SysVol\fitch.corp\Policies\{EC44E774-A908-4583-AE7F-B21D1F38465A}
\User\Scripts\Logon
c:\Program Files\ThinkPad\Utilities
You have a network drive in your path. Does it work any better without
that?
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/
