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 20:09, Pierre A. Humblet wrote:
> At 06:48 PM 4/12/2004 -0500, Brian Ford wrote:
> >On Mon, 12 Apr 2004, 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
> >
> >Ok, I'm confused.  Either I don't understand what you're saying, or
> >the following from the Cygwin User's Guide is too dificult to interpret
> >correctly?
> >
> >http://cygwin.com/cygwin-ug-net/using-cygwinenv.html:
> >
> >(no)smbntsec - if set, use ntsec on remote drives as well (this is the
> >default).
> 
> There is a third possibility: inaccurate documentation.
> 
> /eroot/src/winsup/cygwin: grep 'smbntsec.*=' *.cc
> /eroot/src/winsup/cygwin: grep 'ntsec.*=' *.cc
> environ.cc:    allow_ntsec = true;

Hmm, yes, the allow_smbntsec flag is not set by default and I have no
idea when that disappeared, actually.  Should we revert that or should
we better keep it as it is?  Somehow I have the vague feeling that we
have less complaints about Samba file access for a while...

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]