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 Content-Class: urn:content-classes:message Subject: RE: RESOLVED: cygwin can't write to CIFS... but cmd.exe *can* (more) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 14 Oct 2002 13:31:25 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: <7BFCE5F1EF28D64198522688F5449D5AC1E2C5@xchangeserver2.storigen.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Scott Prive" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9EHVZe27866 > > 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've since moved my environment to the documented variable nosmbntsec > > 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/ > > -- 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/