X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <493BD5D2.A8E8C9EB@dessent.net> Date: Sun, 07 Dec 2008 05:55:30 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: all files seems to be owned by the actual user References: <493B12AE DOT 5FA4A616 AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 Matthias Meyer wrote: > I've tried also ntsec, binmode and "". Why are you doing these things? Are you following somebody's "guide"? Please tell them that they are spreading useless information if that is the case. ntsec is the default. binmode is the default and is irrelevant for files anyway. So "" is the same as "ntsec binmode", and you should not need to set CYGWIN at all in general unless there is a *specific* reason that calls for it. > All of this three list the true file owner with "ls -anlh". > But as before, rsync -a create the files with the user who runs the rsync > command. Also rsync -aA with or without --numeric-ids have this behaviour. > > I would believe that I have a very stupid failure. I can not believe that it > is not possible to backup and restore the file owner. rsync only tries to set the owner when it thinks it has the privilege to do so -- on most POSIX systems this means being the superuser, uid=0. This check in rsync is less than useful on Cygwin where privileges work differently. Thankfully they provide an override in the form of the --super switch. Brian -- 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/