headers
Kyle Lanclos | 1 Mar 2010 23:01
Favicon

Force destination files to specific owner/group

Folks--

I'm working with an old system I set up to copy files from one local
directory to another. I was using rdist for this, but I would prefer
to shift it over to rsync.

The one thing I'm missing is the trivial ability to force the group
owernship of the destination files to a specific group. A read through
the manpage and various searches on the web do not turn up any helpful
hints in this regard.

What I would really like is something like:

rsync --other-options-here --owner=someuser --group=somegroup source/ dest/

Regardless of the source/ ownership and group, files copied to dest/ are
created with owner 'someuser' and group 'somegroup'. Similar to the normal
--owner and --group behavior, this would require --super behavior.

Presumably, if the inspected files in dest/ had different ownership info,
they would be updated to have the 'correct' info, same as if someone had
done a chown -R someuser:somegroup in the destination directory.

If this capability does not exist, would this be a reasonable extension
of the --owner and --group options?

Cheers,

--Kyle
--

--
(Continue reading)

Permalink | Reply | 2 comments |
headers
Bill Campbell | 2 Mar 2010 00:27
Favicon

Re: Force destination files to specific owner/group

On Mon, Mar 01, 2010, Kyle Lanclos wrote:
>Folks--
>
>I'm working with an old system I set up to copy files from one local
>directory to another. I was using rdist for this, but I would prefer
>to shift it over to rsync.
>
>The one thing I'm missing is the trivial ability to force the group
>owernship of the destination files to a specific group. A read through
>the manpage and various searches on the web do not turn up any helpful
>hints in this regard.

If you connect to an rsync daemon you can specify the user and
group on a per-module basis with something like this in your
rsyncd.conf file:

[bills_home]
	uid = bill
	group = staff
	read only = false
	path = /home/bill
	hosts allow = 192.168.0.0/24
	hosts deny *

The appropriate rsync command would be something like

rsync -aHrx /home/bill/ destsys::bills_home/

Bill
--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Khalid J Hosein | 2 Mar 2010 00:35
Picon
Favicon

Rsync copies all files, not just changed files

Hello all,


I have a strange problem where rsync is copying over all files instead of just the ones that have changed.

My setup:
--------------
Backup server runs a script that calls rsync in more or less this form:
   "rsync --rsh=ssh user <at> remote.server.com:/backups/stuff /localbackup" 

Of course, I use a # of options, but the main ones are "-axS" 

Just in case, here are the other options I use: --delete --force --stats --cvs-exclude --bwlimit=100 --exclude-from=rsync-excludes.txt --delete-excluded 


Backing Up Other Machines
----------------------------------------
I've tried and use this same script from the same backup machine against other servers (on different hosts) and found that the exact same set of options worked just fine.

Other Tests
-----------------
I've scoured the lists and Web for solutions and tried things like --size-only, --ignore-times, --checksum and --whole-file. I've broken down my list of options to nothing and tried countless combinations (using dry runs), but haven't had any luck. I keep getting the notorious "Matched data: 0 bytes" in my stats.

At this point, the only thing that I can think of is something to do with the target server (CentOS release 5.4, 2.6.18.8, i686), but I can't think of what exactly.

Any help would be appreciated. TIA.

_KJH
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 4 comments |
headers
Henri Shustak | 2 Mar 2010 00:51
Picon

Re: Rsync copies all files, not just changed files

> I have a strange problem where rsync is copying over all files instead of just the ones that have changed.

If you examine a file at either end which is being re-copied are the permission and ownership settings for
this destination file the same as the permission and ownership on the remote source files. In particular,
check the ownership of the files.

If the ownership is not matching then typically (someone please correct me if I am mistaken) rsync will
re-copy the file.

---------------------------------------------------------------------
This email is protected by LBackup, an open source backup solution.
http://www.lbackup.org

--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 0 comments |
headers
Matt McCutchen | 2 Mar 2010 08:28

Re: Rsync copies all files, not just changed files

On Mon, 2010-03-01 at 15:35 -0800, Khalid J Hosein wrote:
> I have a strange problem where rsync is copying over all files instead
> of just the ones that have changed.

http://rsync.samba.org/FAQ.html#2

Pass -i and see what shows up in the output.

-- 
Matt

--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 1 comment |
headers
samba-bugs | 2 Mar 2010 08:43
Picon
Favicon

DO NOT REPLY [Bug 7194] New: Getting --inplace and --sparse to work together

https://bugzilla.samba.org/show_bug.cgi?id=7194

           Summary: Getting --inplace and --sparse to work together
           Product: rsync
           Version: 3.0.7
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: core
        AssignedTo: wayned <at> samba.org
        ReportedBy: jansen <at> webgods.de
         QAContact: rsync-qa <at> samba.org

I created a small patch to get --inplace and --sparse to work together. The
main problem with this is, as far as I can see, that the write code just skips
blocks of zeroes instead of writing them, as is requested by the --sparse
switch. If the target already exists and has data in places where the source
has zeroes, this data will never get erased.
My patch simply reads these regions first and makes sure they really are zero.
If they are not, it clears them.
It would be good if someone with a deeper knowledge of the implications could
have a look at the patch to see if I missed something.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 7 comments |
headers
samba-bugs | 2 Mar 2010 08:44
Picon
Favicon

DO NOT REPLY [Bug 7194] Getting --inplace and --sparse to work together

https://bugzilla.samba.org/show_bug.cgi?id=7194

------- Comment #1 from jansen <at> webgods.de  2010-03-02 01:44 CST -------
Created an attachment (id=5440)
 --> (https://bugzilla.samba.org/attachment.cgi?id=5440&action=view)
Patch as described

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 0 comments |
headers
Matt McCutchen | 2 Mar 2010 09:14

Re: --progress (without file names)

On Fri, 2010-02-26 at 15:00 +1300, Henri Shustak wrote:
> I am wondering if there is an option which is similar to --progress
> that will not display the file names. A percentage indicator would be
> fine.

See https://bugzilla.samba.org/show_bug.cgi?id=3784 .

-- 
Matt

--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 1 comment |
headers
Matt McCutchen | 2 Mar 2010 09:23

Re: Common memory usage questions

On Wed, 2010-02-10 at 11:34 +0100, Paul Slootman wrote:
> On Tue 09 Feb 2010, Matt McCutchen wrote:
> > 
> > The number of files that rsync tries to maintain in the active file
> > lists at one time is controlled by {MIN,MAX}_FILECNT_LOOKAHEAD in
> > rsync.h.  I did some tests with "ulimit -v", and reducing those values
> > helped significantly.  That still may not be enough to fit rsync into 32
> > MB.
> 
> If you're also preserving hard links (-H), then rsync also needs to
> remember each file that's hardlinked (until link_count entries have been
> seen, assumedly).

There is currently no check to forget files once all of their hard links
have been seen.

Note that when --copy-links is used to make the same dentry show up
multiple places in the source, this check (as well as the initial check
that st_nlink > 1) would not be desirable:

http://lists.samba.org/archive/rsync/2009-May/023201.html

-- 
Matt

--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 0 comments |
headers
samba-bugs | 2 Mar 2010 09:27
Picon
Favicon

DO NOT REPLY [Bug 7195] New: timeout reached while sending checksums for very large files

https://bugzilla.samba.org/show_bug.cgi?id=7195

           Summary: timeout reached while sending checksums for very large
                    files
           Product: rsync
           Version: 3.0.7
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P3
         Component: core
        AssignedTo: wayned <at> samba.org
        ReportedBy: jansen <at> webgods.de
         QAContact: rsync-qa <at> samba.org

When I try to continue the upload of a very large file (400GB, 200GB already
transmitted) with --partial, rsync stops with an error after 10 minutes.
Verbosity shows, that during this time it has transmitted checksums for about
30G worth of data. Increasing the timeout with --timeout=100000 helps. With
this, rsync reaches the point where it transmits new data.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Permalink | Reply | 2 comments |

Gmane