>
> nontsec=smb probably just turns off ntsec entirely. The CYGWIN
> environment variable parser is not that sophisticated.
"oops". I don't suppose I would even notice ntsec being off notice given my limited
needs.
You are probably right, and this is likely a `side effect/parser issue'... I'v
On Mon, Oct 14, 2002 at 01:10:37PM -0400, Scott Prive wrote:
>>>For the archive: Add to NT Environment "nontsec=smb" (no quotes, append
>>>to your existing CYGWIN value).
>>
>>Is this an alternative syntax? I thought it was "nosmbntsec".
>
>This was the first example I found in the archives, and
> > For the archive: Add to NT Environment "nontsec=smb" (no quotes,
> > append to your existing CYGWIN value).
>
> Is this an alternative syntax? I thought it was "nosmbntsec".
>
> Max.
This was the first example I found in the archives, and it worked. It was a discussion
leading up to impli
On Mon, Oct 14, 2002 at 05:50:31PM +0100, Max Bowsher wrote:
>Scott Prive wrote:
>> YES thank you sir! :-D
>>
>> that helped me find this:
>> http://sources.redhat.com/ml/cygwin/2000-12/msg00877.html
>>
>> For the archive: Add to NT Environment "nontsec=smb" (no quotes,
>> append to your existi
Scott Prive wrote:
> YES thank you sir! :-D
>
> that helped me find this:
> http://sources.redhat.com/ml/cygwin/2000-12/msg00877.html
>
> For the archive: Add to NT Environment "nontsec=smb" (no quotes,
> append to your existing CYGWIN value).
Is this an alternative syntax? I thought it was "
YES thank you sir! :-D
that helped me find this:
http://sources.redhat.com/ml/cygwin/2000-12/msg00877.html
For the archive: Add to NT Environment "nontsec=smb" (no quotes, append to your
existing CYGWIN value).
I did search the list before posting, but my search (CIFS, Permission) got ZERO hi
6 matches
Mail list logo
