Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 14 Oct 2002 13:15:20 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: RESOLVED: cygwin can't write to CIFS... but cmd.exe *can* (more) Message-ID: <20021014171520.GA22446@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <7BFCE5F1EF28D64198522688F5449D5AD63A38@xchangeserver2.storigen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7BFCE5F1EF28D64198522688F5449D5AD63A38@xchangeserver2.storigen.com> User-Agent: Mutt/1.4i 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 it worked. It >was a discussion leading up to implimentation, so I assume Corinna >added more than one way to access this feature. nontsec=smb probably just turns off ntsec entirely. The CYGWIN environment variable parser is not that sophisticated. cgf -- 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/