Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<003b01c29030$464e9420$437517d2@astra03>
From:	"Carlo Florendo" <carlo AT astra DOT ph>
To:	<pechtcha AT cs DOT nyu DOT edu>
Cc:	<cygwin AT cygwin DOT com>
References:	<Pine DOT GSO DOT 4 DOT 44 DOT 0211172332260 DOT 4275-100000 AT slinky DOT cs DOT nyu DOT edu>
Subject:	Re: ls problem
Date:	Tue, 19 Nov 2002 17:00:47 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6700

Hi Igor,

I tried disabling ntsec and "ls -l" is still slow.  I'm using
1.3.15-cygwin-1-3-15-1.  "ls -l" and "ls -ln" takes almost the same amount
of time.    On a directory with 3 short text files, the difference, when I
timed "ls -l" and "ls -b", is still considerable.

fcarlo AT ZEUS~
$ time ls -b
a  b  test

real    0m0.024s
user    0m0.030s
sys     0m0.015s

fcarlo AT ZEUS ~
$ time ls -l
total 11
-rw-r--r--    1 fcarlo   None            5 Nov 19 13:58 a
-rw-r--r--    1 fcarlo   None            5 Nov 19 13:58 b
-rw-r--r--    1 fcarlo   None         8283 Nov 19 13:59 test

real    0m1.819s
user    0m0.030s
sys     0m0.000s

Best Regards,

Carlo Florendo






>
> Carlo,
> It would have been more helpful if you had provided your cygwin version,
> but even without it I could venture a guess...  The latest versions of
> cygwin have ntsec on by default, and doing 'ls -l' will result in the user
> lookup in the /etc/passwd (and /etc/group) file.  An easy way to test that
> is to time 'ls -ln' and see if it's faster.  Another test would be to
> *temporarily* turn off ntsec (by adding "nontsec" to your CYGWIN
> environment variable and reloading cygwin1.dll by exiting all running
> cygwin processes).  I say temporarily because ntsec is actually a very
> useful feature to have on, and this is suggested only as a means to find
> out whether it's the culprit.  You can restore the state by either
> changing "nontsec" to "ntsec", or leaving it off altogether, as it's the
> default now, and reloading cygwin1.dll again.
> Igor
> --
> http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
> ZZZzz /,`.-'`'    -.  ;-;;,_ igor AT watson DOT ibm DOT com
>      |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski
>     '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>
> "Water molecules expand as they grow warmer" (C) Popular Science, Oct'02,
p.51
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -