Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Class: urn:content-classes:message Subject: RE: 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 10:18:24 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: <7BFCE5F1EF28D64198522688F5449D5AC1E2C0@xchangeserver2.storigen.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Scott Prive" To: "Scott Prive" , "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9EEIX224457 ...of course, when I do this (in either example), I have cd'd to the CIFS share (/cygdrive/w/ in both cases) Also, the share is authenticated as a test account other than who I am in the shell (shell user=Administrator; CIFS authenticated as user 'foo'). I'm wondering if this has anything to do with my problem, but one would expect to be able to authenticate CIFS shares as other users (I even tried mapping the drive under plain Explorer). What puzzles me is if I start cmd.exe as a subprocess of bash, the writes succeed. -Scott > > Example: > After authentication/mount (via net use), I try `echo "foo" > >myfile.txt` -- 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/