X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <16071836.post@talk.nabble.com> Date: Sat, 15 Mar 2008 13:08:26 -0700 (PDT) From: dand5 To: cygwin AT cygwin DOT com Subject: permissions issue accessing cygwin nfs server from linux machine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mrandraded AT gmail DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hello everyone, I have an nfs server running over cygwin on a XP-Pro box and a SUSE linux machine that needs to access certain disks on the XP box. I set the uids, and gids on the cygwin machine to match those on the linux machine for users that need access (and made sure all others do not map). I am able to mount the XP nfs shares from the linux machine, and the owner, group, and permissions map correctly insofar as 'ls' indicates. However, it appears that some users can write to areas of the XP that they should not be able to and vice versa. Interestingly, all files created by users are automatically owned by root and are become part of the users group. Root maps to an administrator account on the XP machine via /etc/passwd in cygwin. I also tried using a map_static flag in the exports directory, but that had no effect. I'm curious, has anybody has ever encountered this sort of thing before? Anyone have an idea how to resolve this? Thanks for any help. -- View this message in context: http://www.nabble.com/permissions-issue-accessing-cygwin-nfs-server-from-linux-machine-tp16071836p16071836.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/