RE: cannot rsync when source directory lacks write permission

2012-08-10 Thread Steven Levine
In <64fab8215d47a944abdf7de50a3406a219c2dac...@esesscms0353.eemea.ericsson.se>, on 08/10/12 at 09:27 AM, András Porjesz said: Hi András, We may have to agree to disagree on some of this... >Of course, the destination side must have enough rights to achieve what I >need, and an rsyncd running

Re: cannot rsync when source directory lacks write permission

2012-08-10 Thread Paul Slootman
On Fri 10 Aug 2012, András Porjesz wrote: > priority). My assumtion was defaults only used when required, but as I > wrote already, rsyncd overkills client side settings. Of course it does, otherwise you have no security at all, if the client can override whatever the server daemon has configured

RE: cannot rsync when source directory lacks write permission

2012-08-10 Thread András Porjesz
[mailto:bernhard.voel...@siemens-enterprise.com] Sent: Friday, August 10, 2012 10:01 To: András Porjesz; Steven Levine; rsync@lists.samba.org Subject: RE: cannot rsync when source directory lacks write permission András Porjesz wrote (Friday, August 10, 2012 9:27 AM): > I think all the permiss

RE: cannot rsync when source directory lacks write permission

2012-08-10 Thread Voelker, Bernhard
András Porjesz wrote (Friday, August 10, 2012 9:27 AM): > I think all the permission/ownership handling is complicated > (unaccountable, puzzling, peculiar) and the usage is confusing > and annoying I think you didn't get Steven's point: >> [...] The default is >> uid -

RE: cannot rsync when source directory lacks write permission

2012-08-10 Thread András Porjesz
ay, August 09, 2012 21:37 To: rsync@lists.samba.org Subject: RE: cannot rsync when source directory lacks write permission In <64fab8215d47a944abdf7de50a3406a219c2dac...@esesscms0353.eemea.ericsson.se>, on 08/09/12 at 07:54 AM, András Porjesz said: Hi, >Thanks, it looks ok, just i

RE: cannot rsync when source directory lacks write permission

2012-08-09 Thread Steven Levine
In <64fab8215d47a944abdf7de50a3406a219c2dac...@esesscms0353.eemea.ericsson.se>, on 08/09/12 at 07:54 AM, András Porjesz said: Hi, >Thanks, it looks ok, just it is not documented anywhere: >From the ryncd.conf man page uidThis parameter specifies the user name or user ID

RE: cannot rsync when source directory lacks write permission

2012-08-08 Thread András Porjesz
al Message- From: rsync-boun...@lists.samba.org [mailto:rsync-boun...@lists.samba.org] On Behalf Of Kevin Korb Sent: Wednesday, August 08, 2012 19:35 To: rsync@lists.samba.org Subject: Re: cannot rsync when source directory lacks write permission -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It is b

Re: cannot rsync when source directory lacks write permission

2012-08-08 Thread Kevin Korb
sync-boun...@lists.samba.org] On Behalf Of Steven Levine > Sent: Wednesday, August 08, 2012 00:16 To: rsync@lists.samba.org > Subject: Re: cannot rsync when source directory lacks write > permission > > In > , > > on 08/07/12 > at 01:03 PM, "Greg Deback (rsync)"

RE: cannot rsync when source directory lacks write permission

2012-08-07 Thread András Porjesz
n...@lists.samba.org] On Behalf Of Steven Levine Sent: Wednesday, August 08, 2012 00:16 To: rsync@lists.samba.org Subject: Re: cannot rsync when source directory lacks write permission In , on 08/07/12 at 01:03 PM, "Greg Deback (rsync)" said: Hi, >No I think this bug is not rela

Re: cannot rsync when source directory lacks write permission

2012-08-07 Thread Steven Levine
In , on 08/07/12 at 01:03 PM, "Greg Deback (rsync)" said: Hi, >No I think this bug is not related. However, I am wondering : if the >directory is write-protected, even for root, that means it never changes >right ? No. As the code says /* We need to ensure that the dirs in the transfer h

RE: cannot rsync when source directory lacks write permission

2012-08-07 Thread Steven Levine
In <64fab8215d47a944abdf7de50a3406a219c2cfb...@esesscms0353.eemea.ericsson.se>, on 08/07/12 at 07:57 AM, András Porjesz said: Hi, >Probably it is related to this bug: >https://bugzilla.samba.org/show_bug.cgi?id=8844 Well, this behavior is not a bug. It is the way rsync works. If a transfer

Re: cannot rsync when source directory lacks write permission

2012-08-07 Thread Greg Deback (rsync)
lated to this bug: > https://bugzilla.samba.org/show_bug.cgi?id=8844 > Andras > > -Original Message- > From: rsync-boun...@lists.samba.org [mailto:rsync-boun...@lists.samba.org] > On Behalf Of Steven Levine > Sent: Friday, July 27, 2012 20:15 > To: rsync@lists.samba.org

RE: cannot rsync when source directory lacks write permission

2012-08-06 Thread András Porjesz
: cannot rsync when source directory lacks write permission In , on 07/27/12 at 01:26 PM, "Brian J. Murrell" said: Hi, >I seem to be running into a problem where I am trying to rsync from a >source directory that lacks write permissions (i.e. r-xr-xr-x). >Presumably th

Re: cannot rsync when source directory lacks write permission

2012-07-27 Thread Steven Levine
In , on 07/27/12 at 01:26 PM, "Brian J. Murrell" said: Hi, >I seem to be running into a problem where I am trying to rsync from a >source directory that lacks write permissions (i.e. r-xr-xr-x). >Presumably this is because rsync creates the directory on the >destination, then sets the permiss

Re: cannot rsync when source directory lacks write permission

2012-07-27 Thread josephj
Is rsync being run with root privileges for the destination? > I seem to be running into a problem where I am trying to rsync from a > source directory that lacks write permissions (i.e. r-xr-xr-x). > Presumably this is because rsync creates the directory on the > destination, then sets the permis

cannot rsync when source directory lacks write permission

2012-07-27 Thread Brian J. Murrell
I seem to be running into a problem where I am trying to rsync from a source directory that lacks write permissions (i.e. r-xr-xr-x). Presumably this is because rsync creates the directory on the destination, then sets the permissions to match the source and then tries to sync the contents of the d

Re: rsync 3.0.2 with --fileflags on FreeBSD: cannot rsync hardlinked immutable files

2008-06-07 Thread Raphael Becker
On Sat, May 31, 2008 at 09:16:43PM +0200, I wrote: > Hi *, > > it seems rsync with --fileflags isn't able to work on (already) > hardlinked and immutable ("schg") files on FreeBSD. The following > scripts will create a simple example for this behaviour: I forgot to check --force-change but this d

rsync 3.0.2 with --fileflags on FreeBSD: cannot rsync hardlinked immutable files

2008-05-31 Thread Raphael Becker
Hi *, it seems rsync with --fileflags isn't able to work on (already) hardlinked and immutable ("schg") files on FreeBSD. The following scripts will create a simple example for this behaviour: -- #! /bin/sh # # set -x DIR="/var/tmp/rsyn

Re: sol8 - rsync2.5.6 - cannot rsync at all

2003-12-05 Thread Tomasz Ciolek
or the user(oracle). > Wondering whether there is a way not to use "--rsync-path" cmdline. > > thanks again > T > > -Original Message- > From: Wayne Davison [mailto:[EMAIL PROTECTED] > Sent: Friday, December 05, 2003 3:26 PM > To: Wickram, Thushara > Cc: &#x

Re: sol8 - rsync2.5.6 - cannot rsync at all

2003-12-05 Thread Ron DuFresne
--Original Message- From: Wayne Davison [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 3:26 PM To: Wickram, Thushara Cc: '[EMAIL PROTECTED]' Subject: Re: sol8 - rsync2.5.6 - cannot rsync at all On Fri, Dec 05, 2003 at 03:16:45PM -0500, Wickram, Thushara wrote: ksh: rsync:

RE: sol8 - rsync2.5.6 - cannot rsync at all

2003-12-05 Thread Wickram, Thushara
hanks again T -Original Message- From: Wayne Davison [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 3:26 PM To: Wickram, Thushara Cc: '[EMAIL PROTECTED]' Subject: Re: sol8 - rsync2.5.6 - cannot rsync at all On Fri, Dec 05, 2003 at 03:16:45PM -0500,

Re: sol8 - rsync2.5.6 - cannot rsync at all

2003-12-05 Thread Wayne Davison
On Fri, Dec 05, 2003 at 03:16:45PM -0500, Wickram, Thushara wrote: > ksh: rsync: not found This is the key information that the remote ksh is telling you: rsync isn't on the default PATH. You should either fix this, or use the --rsync-path option. ..wayne.. -- To

sol8 - rsync2.5.6 - cannot rsync at all

2003-12-05 Thread Wickram, Thushara
rsync locally but cannot rsync over network ; can rcp over network can rsync locally : [EMAIL PROTECTED]:/apps/oracle/dba> touch test [EMAIL PROTECTED]:/apps/oracle/dba> rcp test test2 [EMAIL PROTECTED]:/apps/oracle/dba> r

Re: Newbie: cannot rsync uppercase files

2001-10-03 Thread Pierre Abbat
On Wednesday 03 October 2001 06:40, Andreas Rebenstorf wrote: > Hi, > > I am using the following command: > > rsync -avzuC --delete -e ssh --stats --progress > someone@someware:/home/someone /home/someone > > The problem is now that all uppercase files and directorys are saved as > lowercase. Exam

Newbie: cannot rsync uppercase files

2001-10-03 Thread Andreas Rebenstorf
Hi, I am using the following command: rsync -avzuC --delete -e ssh --stats --progress someone@someware:/home/someone /home/someone The problem is now that all uppercase files and directorys are saved as lowercase. Example: TEST.TXT will be saved as test.txt On the next start of rsync all the

cannot rsync

2000-10-09 Thread Mate Wierdl
I am sure I am missing something: I have [ftp] path = /home/ftp/pub comment = ftp export area [alpha] path = /home/ftp/pub/alpha comment = alpha software [qmail] path = /home/ftp/pub/qmail c