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
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
[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
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 -
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
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
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
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)"
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
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
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
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
: 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
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
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
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
16 matches
Mail list logo
