On Wed, May 15, 2013 at 11:17 AM, Lokesh Walase wrote:
>
>
>
> On Sun, May 12, 2013 at 4:46 PM, Lokesh Walase wrote:
>
>>
>>
>>
>> On Sat, May 11, 2013 at 7:54 PM, Scott Wiersdorf wrote:
>>
>>> On Sat, May 11, 2013 at 09:56:34AM +0530, Lokesh Walase wrote:
>>> > In "cp" command, we have "-i" optio
On 15/05/2013 11:26 AM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, it will change the permissions and ownerships even if it doesn't
touch the data.
Thank you
Carl
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, it will change the permissions and ownerships even if it doesn't
touch the data.
On 05/14/13 21:09, Carl Brewer wrote:
> On 15/05/2013 10:57 AM, Kevin Korb wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> OK, since your timestamps a
On 15/05/2013 10:57 AM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, since your timestamps are all a mess you have 2 choices...
1. Assume that all files on one system are correct and rsync --archive
from it to the other. Rsync will go through all the data but it will
onl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, since your timestamps are all a mess you have 2 choices...
1. Assume that all files on one system are correct and rsync --archive
from it to the other. Rsync will go through all the data but it will
only actually transfer the differences. It wil
On 15/05/2013 10:38 AM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If the timestamps are the same then rsync with -a should just fix the
ownerships and permissions.
That doesn't seem to deal with older files though, which is most of
them, at least as far as I can tell. M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If the timestamps are the same then rsync with -a should just fix the
ownerships and permissions.
If the timestamps are not the same then you could do it with getfacl
and setfacl as they can use a text file as an intermediary however
your next questio
G'day,
I'm in the process of fixing a long broken rsync backup on a couple of
servers. The old system rsync'd a Linux (CentOS 5) server onto a
Opensolaris/OpenIndiana server but didn't worry about ownership or
permissions, across an expensive WAN link. All the ownerships and
permissions ar
https://bugzilla.samba.org/show_bug.cgi?id=9882
Summary: Incorrect exit code when sender over SSH is killed
with SIGTERM
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Severity: