X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=3.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,TVD_RCVD_IP X-Spam-Check-By: sourceware.org From: "Jan Alphenaar" To: Subject: FW: Rsync question on version 3.0.4 Date: Sat, 23 May 2009 23:29:36 +0200 Message-ID: <4DE96E796DB0449899E072E5B8C6E0DE@napoleon> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 FYI -----Oorspronkelijk bericht----- Van: Jan Alphenaar [mailto:jan DOT alphenaar AT dotcolour DOT com]=20 Verzonden: zaterdag 23 mei 2009 20:18 Aan: 'Lapo Luchini' Onderwerp: RE: Rsync question on version 3.0.4 Hi Lapo, Thanks for giving an answer. Without the -p option the rights on the directory on my local PC look prett= y strange to me (000). Too bad I was looking to this directory with Windows= Explorer only and not with a CygWin window, otherwise I could have figured= this out myself... =20 With the -p option the rights come from the serverside, which is better. It= now seems to work correctly Thanks a lot for helping me out. Regards, Jan -----Oorspronkelijk bericht----- Van: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] Namens Lapo L= uchini Verzonden: zaterdag 23 mei 2009 13:31 Aan: cygwin AT cygwin DOT com Onderwerp: Re: Rsync question on version 3.0.4 Jan Alphenaar wrote: > When I copy over a directory from my server to my local pc with rsync, it= is > not possible to open the local directory Do you mean the origin has 644 files and the destination has 000 file permissions? Also as you're not using -p the destination file permission are not copied from the origin ones: When this option is off, permissions are set as follows: o Existing files (including updated files) retain their existing permissions, though the =E2=88=92=E2=88=92executability option might c= hange just the execute permission for the file. o New files get their =E2=80=9Cnormal=E2=80=9D permission bits set to th= e source file=E2=80=99s permissions masked with the receiving directory=E2=80= =99s default permissions (either the receiving process=E2=80=99s umask, or the permissions specified via the destination directory=E2=80=99s default = ACL), and their special permission bits disabled except in the case where a new directory inherits a setgid bit from its parent directory. --=20 Lapo Luchini - http://lapo.it/ -- 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/ -- 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/