This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch]: path.cc


On Apr 12 19:06, Pierre A. Humblet wrote:
> I have also observed abnormal behavior on NT4.0
> 1) ls uses ntsec even on remote drives without smbntsec
> 
> /> echo $CYGWIN
> bash: CYGWIN: unbound variable
> ~> uname -a
> CYGWIN_NT-4.0 myhost 1.5.9(0.112/4/2) 2004-03-18 23:05 i686 unknown unknown
> Cygwin
> ~> ls -ld ~
> drwxr-xr-x    1 PHumblet Clearuse        0 Apr 12 10:16 /h/

Woops, I got a write accessor wrong.  Fixed and changed to be somewhat
cleaner defined.

> ~> uname -a
> CYGWIN_NT-4.0 myhost 1.5.10(0.113/4/2) 2004-04-12 00:16 i686 unknown
> unknown Cygwin
> ~> ls -ld ~
> d---------+  22 Administ Domain A        0 Apr 12 10:16 /h/
> 
> 
> 2) The system has become unbearably slow.
>  
>  2771   45904 [main] ls 410 get_file_attribute: file: h:\Job
> 1091290 1137194 [main] ls 410 cygpsid::debug_print: get_sids_info: owner
> SID = S-1-5-32-544
> 
> I think it's related to
> http://www.cygwin.com/ml/cygwin/2003-03/msg01760.html

Fortunately these NT 4 bugs are Win32 API bugs, not native NT API bugs.
I replaced the whole get_nt_object_attribute functionality by calls
to the native NtQuerySecurityObject function and tested on NT 4.  File
access as well as registry access are both as quick as on my XP system
now, AFAICS.

Thanks for the report,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]