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: 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 12:00:34 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: <7BFCE5F1EF28D64198522688F5449D5AD63A37@xchangeserver2.storigen.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Scott Prive" To: "Donald MacVicar" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9EG0tp10848 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 hits. Surprisingly, even the refined search (smb nontsec) got only a few hits... all talking about this problem BEFORE the feature code was added (discussion was still taking place as to what the variable should be, including "ilikepie=yes" :-) Interestingly, some folks had suggested that the Cygwin default mirror CMD.EXE behavior, as it would be "less confusing" (I agree). I didn't see a reply to that suggestion. This would be a great addition to the FAQ IMO, even if it only references a search to the archives, because you need to know the answer to get a hit on this search... -Scott > -----Original Message----- > From: Donald MacVicar [mailto:donald AT dramgo DOT co DOT uk] > Sent: Monday, October 14, 2002 11:12 AM > To: cygwin AT cygwin DOT com > Subject: Re: Cygwin can't write to CIFS... but cmd.exe *can* (more) > > > There is loads of stuff in the list archives on this. If you > have local > user accounts on the Win machine (rather than domain accounts) and > access using shares using the unix account then the UID/GID are > different, you can set CYGWIN too some value - I think it is > smbnontsec, > someone can correct me if I cam wrong. > > Using a different user for authentication on the samba share that the > current user will work fine under win but because of the UID changes > will not work under cygwin unless the smbnontsec is added to > the CYGWIN > enviroment variable. > > A search of the archives will give you plenty more on this. > > Donald. > > Igor Pechtchanski wrote: > > >Scott, > >I've had some trouble with file permissions on samba shares > under Win2k. > >Not anything as severe as yours, but the files created on a > share didn't > >inherit the world read permissions of the directories (and > those couldn't > >be set). I wonder if these are related? > > Igor > > > >On Mon, 14 Oct 2002, Scott Prive wrote: > > > > > > > >>...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/ > > -- 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/