Re: Ownership and permissions when syncing directory contents

> > That is as documented. You are requesting that the directory is synced > to c, preserving all attributes (due to -a) so rsync does that. > Ah... the attributes of the containing directory are transferred to the containing directory on the destination. I read that but failed to absorb it. I

Re: Ownership and permissions when syncing directory contents

On Fri 20 Jan 2017, John Lane wrote: > > When you rsync a directory, say `$rsync mydir/ ...` with the trailing > slash, the destination directory is changed to the ownership, > permissions and timestamp of `mydir`. > $ rsync -a a/ b/ c > $ ls -ld c > drwxr-xr-x

Ownership and permissions when syncing directory contents

When you rsync a directory, say `$rsync mydir/ ...` with the trailing slash, the destination directory is changed to the ownership, permissions and timestamp of `mydir`. Consider this simple example $ mkdir test $ cd test $ mkdir a b $ touch -d '01 jan 1980' a/A

RE: ownership and permissions using rsync in daemon mode

That worked like a champ. Thank you. From: Kevin Korb [via Samba] [mailto:ml-node+s2283325n4655305...@n4.nabble.com] Sent: Friday, October 18, 2013 2:41 PM To: Kevin Mullen Subject: Re: ownership and permissions using rsync in daemon mode -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When fake

Re: ownership and permissions using rsync in daemon mode

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When fake super is active rsync stores all ownership and permission info within extended attributes instead of the filesystem. On 10/18/13 13:42, kevin mullen wrote: > I've tried as best I can to get this worked out, and crawled the >

ownership and permissions using rsync in daemon mode

I've tried as best I can to get this worked out, and crawled the web and the documentation but I just can't seem to figure out how to maintain ownership and permissions from the sending side using rsync in daemon mode. I feel I have to be missing something stupid with the proper use

[Bug 9770] Preserving ownership and permissions does not work

https://bugzilla.samba.org/show_bug.cgi?id=9770 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: Using rsync to just -resync permissions and ownership?

On Tue, May 14, 2013 at 6:09 PM, Carl Brewer wrote: > so --archive will overwrite permissions on files that it's not replacing? > Yes, but you need to be very sure that it doesn't overwrite changed files that you wanted to keep. For safety, you can use --backup along with --backup-dir and check

Re: Using rsync to just -resync permissions and ownership?

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

Re: Using rsync to just -resync permissions and ownership?

-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

Re: Using rsync to just -resync permissions and ownership?

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

Re: Using rsync to just -resync permissions and ownership?

-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

Re: Using rsync to just -resync permissions and ownership?

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

Re: Using rsync to just -resync permissions and ownership?

e 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 are different to the original box on the > OI box. > > I now

Using rsync to just -resync permissions and ownership?

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 ownersh

[Bug 9770] Preserving ownership and permissions does not work

aborting rsync before it > finishes? Rsync creates directories with default ownership and 700 > permissions > to make sure it doesn't get a permission denied error when it tries to add > files. Once it is done with a directory it goes back and sets the ownership, > group, permi

[Bug 9770] Preserving ownership and permissions does not work

creates directories with default ownership and 700 permissions to make sure it doesn't get a permission denied error when it tries to add files. Once it is done with a directory it goes back and sets the ownership, group, permissions, and timestamps. -- Configure bugmail: https://bugzilla.samb

[Bug 9770] Preserving ownership and permissions does not work

https://bugzilla.samba.org/show_bug.cgi?id=9770 --- Comment #1 from Kevin Korb 2013-04-06 22:56:16 UTC --- Try: rsync -vai Source/ Dest/ Also, verify that you are running rsync as root and that the target filesystem supports such features. -- Configure bugmail: https://bugzilla.samba.org/user

[Bug 9770] New: Preserving ownership and permissions does not work

https://bugzilla.samba.org/show_bug.cgi?id=9770 Summary: Preserving ownership and permissions does not work Product: rsync Version: 3.0.9 Platform: x64 OS/Version: Linux Status: NEW Severity: critical Priority: P5

RE: [Bug 8844] rsyncd ownership handling

] rsyncd ownership handling https://bugzilla.samba.org/show_bug.cgi?id=8844 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 8844] rsyncd ownership handling

poorly in that it is trying to say that the process runs as that user. The gid parameter is similar. Both default to running the process as "nobody", which has no rights to chown files to other users. So, if you want to preserve ownership, you must run the receiving process as root, or perh

[Bug 8844] New: rsyncd ownership handling

https://bugzilla.samba.org/show_bug.cgi?id=8844 Summary: rsyncd ownership handling Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core

[Bug 6927] Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc.

https://bugzilla.samba.org/show_bug.cgi?id=6927 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 8268] Wrong unchanged_attrs test for symlink ownership

https://bugzilla.samba.org/show_bug.cgi?id=8268 Wayne Davison changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 8268] New: Wrong unchanged_attrs test for symlink ownership

https://bugzilla.samba.org/show_bug.cgi?id=8268 Summary: Wrong unchanged_attrs test for symlink ownership Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5

DO NOT REPLY [Bug 7773] Please add a switch to preserve ownership on the receiving side

https://bugzilla.samba.org/show_bug.cgi?id=7773 m...@mattmccutchen.net changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

DO NOT REPLY [Bug 7773] Please add a switch to preserve ownership on the receiving side

|WORKSFORME | --- Comment #2 from m...@mattmccutchen.net 2010-11-06 13:16 CST --- I think the request is for recreated destination files to keep the same ownership they had, rather than taking the default ownership of the receiver, when --owner and --group are off. (Of

DO NOT REPLY [Bug 7773] Please add a switch to preserve ownership on the receiving side

||WORKSFORME --- Comment #1 from way...@samba.org 2010-11-06 10:56 CST --- Specify --owner (and possibly --group, or just use --archive). Just make sure the receiver is authorized to set ownership (you can use --super to force it to try). -- Configure bugmail: https

DO NOT REPLY [Bug 7773] New: Please add a switch to preserve ownership on the receiving side

https://bugzilla.samba.org/show_bug.cgi?id=7773 Summary: Please add a switch to preserve ownership on the receiving side Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity

DO NOT REPLY [Bug 6927] Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc.

lso ignore files whose times differ by exactly 3600 or > 3601 > seconds too. This would help when rsyncing files created near the time of the > daylight savings time switchover. That is a hack. > * Ignore ownership, hard links, symlinks, etc. This will reduce useless > errors sh

DO NOT REPLY [Bug 6927] Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc.

https://bugzilla.samba.org/show_bug.cgi?id=6927 --- Comment #1 from jasonspi...@gmail.com 2009-11-24 22:20 CST --- Typo. I meant "Please credit Kevin Korb

DO NOT REPLY [Bug 6927] New: Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc.

https://bugzilla.samba.org/show_bug.cgi?id=6927 Summary: Add a --fat option to ignore 1-second time diffs, ownership, hard links, symlinks, etc. Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status

Re: Unix file ownership for wide open directories

16:05 /foo/file_b > > I'm trying to avoid using rsynd as we're paranoid about security. (We > change root password on a regular basis. The solutions indicate that I > may have to change the secrets file each time.) > > Any suggestions on preserving the file ownership in this

Re: Unix file ownership for wide open directories

; do strange things.) > > If I use rsync as user1 all the files on the destination server are > owned by user1. I.E. > > ls -l /foo/* > total 0 > -rw-r--r-- 1 user1other 10 Oct 30 16:05 /foo/file_a > -rw-r--r-- 1 user1other 30 Oct 30 16:0

Unix file ownership for wide open directories

nge the secrets file each time.) Any suggestions on preserving the file ownership in this case? JC -- 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://ww

DO NOT REPLY [Bug 6578] put out skipped dirs files w/ perms and ownership

https://bugzilla.samba.org/show_bug.cgi?id=6578 toralf.foers...@gmx.de changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 6578] put out skipped dirs files w/ perms and ownership

https://bugzilla.samba.org/show_bug.cgi?id=6578 --- Comment #3 from m...@mattmccutchen.net 2009-07-28 17:53 CST --- Yes. If you need to append the * to every line of an existing exclude file, you can do that in an automated fashion with sed. -- Configure bugmail: https://bugzilla.

DO NOT REPLY [Bug 6578] put out skipped dirs files w/ perms and ownership

https://bugzilla.samba.org/show_bug.cgi?id=6578 --- Comment #2 from toralf.foers...@gmx.de 2009-07-28 02:44 CST --- Fine - but can I use the same syntax w/ using an exclude file ? -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving thi

DO NOT REPLY [Bug 6578] put out skipped dirs files w/ perms and ownership

https://bugzilla.samba.org/show_bug.cgi?id=6578 --- Comment #1 from m...@mattmccutchen.net 2009-07-27 19:55 CST --- You can exclude all the contents of the temporary dirs and still copy the dirs themselves: --exclude='/tmp/*' . -- Configure bugmail: https://bugzilla.samba.org/userp

DO NOT REPLY [Bug 6578] New: put out skipped dirs files w/ perms and ownership

https://bugzilla.samba.org/show_bug.cgi?id=6578 Summary: put out skipped dirs files w/ perms and ownership Product: rsync Version: 3.0.5 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority

Re: ownership

On 7/30/07, boricua <[EMAIL PROTECTED]> wrote: > in that case it just gave a user of 500? > > 4.0K drwxr-xr-x 14 500502 4.0K 2007-07-15 08:08 zoe/ As you hinted earlier, that probably means there's no user "zoe" on the destination, so rsync preserved the owner by number instead of name. If y

Re: ownership

On Mon, 30 Jul 2007 21:33:30 -0400 "Matt McCutchen" <[EMAIL PROTECTED]> wrote: > On 7/30/07, boricua <[EMAIL PROTECTED]> wrote: > > not sure if i misunderstood the documentation but my understanding is > > the -a option preserves ownership and permissions on

Re: ownership

On 7/30/07, boricua <[EMAIL PROTECTED]> wrote: > not sure if i misunderstood the documentation but my understanding is > the -a option preserves ownership and permissions on transfer. > > i did a remote test and i see ownership changed > is that becuase user does not ex

ownership

not sure if i misunderstood the documentation but my understanding is the -a option preserves ownership and permissions on transfer. i did a remote test and i see ownership changed is that becuase user does not exist in the remote box 4.0K drwxr-xr-x 14 zoe zoe 4.0K 2007-07-15 08:08

Re: File/Folder Ownership - Cygwin/Rsync - Is it possible to get around rsync taking file ownership?

On 7/24/07, jhurd8025 <[EMAIL PROTECTED]> wrote: This takes ownership away from the administrators group, thus disallowing inherited permissions. I bet there's some way to achieve the effect you want even without the administrators group owning the files. How exactly are th

Re: File/Folder Ownership - Cygwin/Rsync - Is it possible to get around rsync taking file ownership?

On Wed, Jul 25, 2007 at 11:57:15AM -0700, jhurd8025 wrote: > The only way around this would be to use the rsyncd which runs as root, and > is not possible (security wise) in our enviroment. If the receiving rsync isn't running as root (or whatever the super-user is), then it is impossible for it t

Re: File/Folder Ownership - Cygwin/Rsync - Is it possible to get around rsync taking file ownership?

Thanks Matt, I'm beginning to believe this isn't possible. I've tried both nontsec and ntsec with no luck, and I've tried with and without -o -p -g. Still takes ownership from administrators and gives it to the rsync user. The only way around this would be to use the rsync

Re: File/Folder Ownership - Cygwin/Rsync - Is it possible to get around rsync taking file ownership?

On 7/24/07, jhurd8025 <[EMAIL PROTECTED]> wrote: Case point: 2 Servers (both with Windows Server 2k3 & cygwin). Running ssh on the destination server. Problem: The rsync user will take ownership over any files copied over from the source server. This takes ownership awa

Re: File/Folder Ownership - Cygwin/Rsync - Is it possible to get around rsync taking file ownership?

they are on the source machine. jhurd8025 wrote: > > Case point: 2 Servers (both with Windows Server 2k3 & cygwin). Running ssh > on the destination server. > > Problem: The rsync user will take ownership over any files copied over > from the source server. This takes o

File/Folder Ownership - Cygwin/Rsync - Is it possible to get around rsync taking file ownership?

Case point: 2 Servers (both with Windows Server 2k3 & cygwin). Running ssh on the destination server. Problem: The rsync user will take ownership over any files copied over from the source server. This takes ownership away from the administrators group, thus disallowing inherited permiss

Re: rsync'd files&dirs saved as user:group = "unknown":"unknown", NOT original ownership

e string "uid=1234" on the sending side (no matter what), but the receiving side's list will only contain this string if rsync believes that it is running in super-user mode with ownership being preserved. while rtfm'ing and poking around, i believe i've stumbled onto t

Re: rsync'd files&dirs saved as user:group = "unknown":"unknown", NOT original ownership

's list will only contain this string if rsync believes that it is running in super-user mode with ownership being preserved. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

rsync'd files&dirs saved as user:group = "unknown":"unknown", NOT original ownership

hello, i've rsync installed: rsync version 2.6.9pre3 protocol version 29 Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, inplace, no IPv6, 32-bit system inums, 64-bit internal inums i'm PULLing via rsync+ssh from BoxA to BoxB, eg:

Re: Storing ownership / device nodes without root

On Sat, Oct 28, 2006 at 05:15:06PM +0200, Wesley W.Terpstra wrote: > I would send patches, but I find it quite difficult to get patches > against patches. I actually don't like patches against patches. Your prior posting had a patch against some pre-patched source, and that's the clearest way t

Re: Storing ownership / device nodes without root

On Oct 28, 2006, at 12:58 AM, Wayne Davison wrote: Yeah, the error checking is not up-to-snuff yet. Sorry, when you said you'd checked it in, I assumed that meant you were done with it and the final version was committed. Now I've seen: http://archives.free.net.ph/thread/ 20061028.062640.

Re: Storing ownership / device nodes without root

On Fri, Oct 27, 2006 at 01:37:45PM +0200, Wesley W. Terpstra wrote: > ... fake-super is never sent from the client...? That code is just to prevent mischief from someone that might tweak their client to send the option to a daemon. > Your chmod change broke symlinks. do_chmod needs to see if the

Re: Storing ownership / device nodes without root

On Oct 27, 2006, at 9:46 AM, Wayne Davison wrote: http://rsync.samba.org/ftp/unpacked/rsync/patches/fake-super.diff Does any of my patch remain?? ;-) I don't understand the logic of clientserver.c: if (lp_fake_super(i)) am_root = -1; else if (am_root < 0) /* Trea

Re: Storing ownership / device nodes without root

On Fri, Oct 27, 2006 at 03:55:09AM +0200, Wesley W. Terpstra wrote: > There are a couple bits I think belong in xattrs.patch instead. > Specifically, storing EAs before ACLs in rsync.c and including the > removexattr method. I agree. I've added those bits to the xattr.diff. At some point the x

Re: Storing ownership / device nodes without root

On Oct 26, 2006, at 5:45 PM, Wayne Davison wrote: I think this would be a useful thing to support. I don't like the options tied in to source/dest, though as that makes it harder to reverse a copy. I think that adding a single option, --fake-super (since we already have --super) that does not g

Re: Storing ownership / device nodes without root

On Thu, Oct 26, 2006 at 01:25:56PM +0200, Wesley W. Terpstra wrote: > I was thinking of options like '--source-fake-root' and '--dest-fake- > root'. The client turns '--dest-fake-root' into '--source-fake-root' > on the remote rsync process. I think this would be a useful thing to support. I d

Storing ownership / device nodes without root

Right now, if you want a faithful backup of a system, you must either have root access on the target machine (for chown, mknod, ...), or you have to arrange for fakeroot/pretendroot to wrap itself around the rsync server to catch all these permissions/etc and keep them in a database file. A

Re: Saving ownership as non-root

Paul Slootman wrote: > Hence although it would look like you could use rsync to backup device > nodes and so on via fakeroot, as soon as the fakeroot session is ended, > the information is gone. There is some support for persistent storage of > the fake info, but that's not perfect; I wouldn't rel

Re: Saving ownership as non-root

ync is running as root, or (2) someone that has a privileged admin account that can preserve file ownership without being UID 0. The first case is more likely, and solves the problem where an option like -o (implied by -a) might be silently ignored if the remote rsync isn't running as root

Re: Saving ownership as non-root

Hi Paul, hi everyone else! (-: First, thank you for your reply on my topic! On Wed, Aug 16, 2006 at 04:24:57PM +0200, Paul Slootman wrote: > On Wed 16 Aug 2006, Robert Siemer wrote: > > > > Out of curiosity: What (backup) solutions do you use to let rsync store > > devic

Re: Saving ownership as non-root

On Wed 16 Aug 2006, Robert Siemer wrote: > > Out of curiosity: What (backup) solutions do you use to let rsync store > device files and ownership permissions without root privileges? > > I found out about "fakeroot" so far. Is there actually a practical use > for th

Saving ownership as non-root

Hello everybody! Out of curiosity: What (backup) solutions do you use to let rsync store device files and ownership permissions without root privileges? I found out about "fakeroot" so far. Is there actually a practical use for the "--super" option? I didn't find any

RE: cwrsync server 2.0.4 / winxp / ownership problems?

#x27;; 'Erik Jacobs' Cc: rsync@lists.samba.org Subject: RE: cwrsync server 2.0.4 / winxp / ownership problems? It is possible to instruct cygwin not to reflect permission changes to windows' file system. This can be done by specifying CYGWIN=nontsec. In this case, all permission relat

RE: cwrsync server 2.0.4 / winxp / ownership problems?

sts.samba.org > Subject: Re: cwrsync server 2.0.4 / winxp / ownership problems? > > On Tue, Jan 31, 2006 at 01:13:47PM -0500, Erik Jacobs wrote: > > I didn't think that CHMod would have any effect in windows?? > > I assumed that the cygwin library would map the inte

Re: cwrsync server 2.0.4 / winxp / ownership problems?

On Tue, Jan 31, 2006 at 01:13:47PM -0500, Erik Jacobs wrote: > I didn't think that CHMod would have any effect in windows?? I assumed that the cygwin library would map the internal mode change into an appropriate external change on the filesystem. However, since I try to avoid MS Windows whenever

RE: cwrsync server 2.0.4 / winxp / ownership problems?

>The version of rsync in CVS has an option named --chmod that lets you >request permission changes for the copied files, so using that as the I didn't think that CHMod would have any effect in windows?? Are you referring to the rsync in CVS for cwrsync? -Erik -- To unsubscribe or change options

Re: cwrsync server 2.0.4 / winxp / ownership problems?

On Mon, Jan 30, 2006 at 04:25:01PM -0500, Erik Jacobs wrote: > Whenever I run rsync to send files to another machine, the read-only > flag gets set. The version of rsync in CVS has an option named --chmod that lets you request permission changes for the copied files, so using that as the client ve

RE: cwrsync server 2.0.4 / winxp / ownership problems?

in c:\cv7\windows\ and the properties had been reset to read-only!! Any ideas? -Original Message- From: Tevfik Karagülle [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 5:35 PM To: 'Erik Jacobs' Cc: rsync@lists.samba.org Subject: RE: cwrsync server 2.0.4 / winxp / ow

RE: cwrsync server 2.0.4 / winxp / ownership problems?

--Original Message- From: Tevfik Karagülle [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 5:35 PM To: 'Erik Jacobs' Cc: rsync@lists.samba.org Subject: RE: cwrsync server 2.0.4 / winxp / ownership problems? Hi Erik, Since cwrsync contains some windows-specific arrangements not

RE: cwrsync server 2.0.4 / winxp / ownership problems?

#x27; Cc: rsync@lists.samba.org Subject: RE: cwrsync server 2.0.4 / winxp / ownership problems? Hi Erik, Since cwrsync contains some windows-specific arrangements not directly related to rsync itself, I've established a cwrsync discussion forum half a year ago. It is available at http:/

RE: cwrsync server 2.0.4 / winxp / ownership problems?

ourceforge.net/projects/sereds > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Erik Jacobs > Sent: 30. januar 2006 22:25 > To: rsync@lists.samba.org > Subject: cwrsync server 2.0.4 / winxp / ownership problems? > > Hi a

cwrsync server 2.0.4 / winxp / ownership problems?

ad only. Is it possible to change the cwrsync configuration so that it runs as the same user that the operator logs in as? I'm thinking that for some reason windows is getting confused and setting the ownership to the cwrsync user and that's why the operator user sees the file as read-on

[Bug 3253] Feature request - Sync perms/ownership/time etc but with no file transfer

https://bugzilla.samba.org/show_bug.cgi?id=3253 --- Comment #2 from [EMAIL PROTECTED] 2005-11-16 18:51 MST --- Created an attachment (id=1575) --> (https://bugzilla.samba.org/attachment.cgi?id=1575&action=view) perl script solution I enjoy coding simple perl scripts like this, so he

[Bug 3253] Feature request - Sync perms/ownership/time etc but with no file transfer

able to parse the output of "ls -lR" from one system and apply the permissions/ownership/groups to the matching files on another system (skipping those that don't exist). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail becau

[Bug 3253] New: Feature request - Sync perms/ownership/time etc but with no file transfer

https://bugzilla.samba.org/show_bug.cgi?id=3253 Summary: Feature request - Sync perms/ownership/time etc but with no file transfer Product: rsync Version: 2.6.7 Platform: All OS/Version: All Status: NEW

Re: How to preserve ownership with rsync over SSH

On Monday 01 Aug 2005 14:56, Olivier BONHOMME wrote: > Hello everybody, > > I am discovering rsync and I have a problem about preserving ownership > and permissions. I want to mirror a web tree with rsync over ssh. I set > up a module on my rsync server and on the rsync client, I us

RE: How to preserve ownership with rsync over SSH

, 2005 8:57 AM To: rsync@lists.samba.org Subject: How to preserve ownership with rsync over SSH Hello everybody, I am discovering rsync and I have a problem about preserving ownership and permissions. I want to mirror a web tree with rsync over ssh. I set up a module on my rsync server and on the

How to preserve ownership with rsync over SSH

Hello everybody, I am discovering rsync and I have a problem about preserving ownership and permissions. I want to mirror a web tree with rsync over ssh. I set up a module on my rsync server and on the rsync client, I use the options -o and -p in order to preserve ownership et permissions. The

maintaining ownership with cygwin/rsync?

trying to use rsync (2.6.3) from the most recent cygwin distribution.   It works fine, except that when doing an “rsync –a” or “rsync –archive”, I’m expecting the ownership to be maintained, and it is not – the destination owner is always “Administrator”, which is different from the source (I’m

Re: Client-initiated backup and file ownership

On 2005-03-01 16:26:56 -0500, Andrew Gideon wrote: > So is there a way around this? I was thinking about having the client run a > program on the backup server which causes the usual server-initiated backup > to occur. But how would this work if the laptop is behind a NAT device? Use ssh (with f

Client-initiated backup and file ownership

rsync process can run as root on the backup server, and so it can set the stored files' ownerships as desired. Of course, there are other advantages to server-initiated backup, but the file ownership issue is relevant to my question. As nice as server-initiated backup is, there are certain case

Re: Ownership

I just thought of something else that I should have thought of earlier: if you're using a chroot=yes setup for an rsync daemon, you must put the appropriate files into the chroot area for rsync to do any mapping of UIDs and GIDs (as explained in the man rsyncd.conf manpage). For instance, create a

Re: Ownership

How can I check whether rsync uses /etc/nsswitch.conf or not? I'd suggest finding a Linux forum to ask that question (and first googling to see if the answer is already out there). I'd also suggest creating a simple test program that just tries to lookup "testuser" using getpwnam() (you could eas

Re: Ownership

I just thought of something else that I should have thought of earlier: if you're using a chroot=yes setup for an rsync daemon, you must put the appropriate files into the chroot area for rsync to do any mapping of UIDs and GIDs (as explained in the man rsyncd.conf manpage). For instance, create a

Re: Ownership

On Tue, Sep 28, 2004 at 05:15:55PM +0200, Essyug wrote: > How can I check whether rsync uses /etc/nsswitch.conf or not? I'd suggest finding a Linux forum to ask that question (and first googling to see if the answer is already out there). I'd also suggest creating a simple test program that just

Re: Ownership

1. The receiving rsync isn't linked with the right library for getpwent() to find the name on that Linux system. This could indeed be the case, but I don't know how to check/solve this. I'm using nsswitch with winbind... /etc/nsswitch.conf: passwd: compat winbind group: compat wi

Re: Ownership

On Tue, Sep 28, 2004 at 10:26:32AM +0200, Essyug wrote: > I really think it's on the rsync/cygwin side which probably > sends the numeric id instead of the name, or simply doesn't send the > name/uid map (although my user is known on this side, too). No, the test output you saw proves that is no

Re: Ownership

Lookup of `testuser' failed Exactly as I expected. As long as there are no weird non-visible characters in that name (which I assume there are not), then you just need to figure out how to get the "testuser" into your defined users on the Linux box. (Try running something like "groups testuser"

Re: Ownership

On Fri, Sep 24, 2004 at 04:07:21PM +0200, Essyug wrote: > I don't see anything like that, even with "strace -f". Sorry, I wasn't thinking straight because getpwnam() is a library routine, not a system call, so you'll see things like the open for /etc/passwd that was caused by the call, but not the

Re: Ownership

Does the client side send 11385 or "testuser"? Or both? It sends both (it sends a mapping table of UID/name pairs before it sends the UIDs attached to the file-info). The fact that your server got the name but didn't change the UID to the right value indicates to me that the getpwnam() call didn'

Re: Ownership

On Fri, Sep 17, 2004 at 09:29:41AM +0200, Essyug wrote: > Does the client side send 11385 or "testuser"? Or both? It sends both (it sends a mapping table of UID/name pairs before it sends the UIDs attached to the file-info). The fact that your server got the name but didn't change the UID to the

Re: Ownership

All I get running with - is the gid... That is because rsync doesn't believe that it is root. I think I should modify rsync so that it outputs the uid when it is the sender even when it is not root. What your output doesn't show is what the receiver thinks the uid is (which will show if it be

Re: Ownership

On Tue, Sep 14, 2004 at 09:22:05AM +0200, Essyug wrote: > All I get running with - is the gid... That is because rsync doesn't believe that it is root. I think I should modify rsync so that it outputs the uid when it is the sender even when it is not root. What your output doesn't show is wh

Re: Ownership

testuser:x:1:1:testuser:/home/DOMAIN/testuser:/bin/false [...] DOMAIN\testuser:x:1:1:testuser:/home/DOMAIN/testuser:/bin/false I'd suggest running with expanded levels of -v until you see what user & group names are getting sent. I'd bet that the two strings don't match (as they d

Re: Ownership

On Thu, Sep 09, 2004 at 11:46:48AM +0200, Essyug wrote: > testuser:x:1:1:testuser:/home/DOMAIN/testuser:/bin/false [...] > DOMAIN\testuser:x:1:1:testuser:/home/DOMAIN/testuser:/bin/false I'd suggest running with expanded levels of -v until you see what user & group names are gettin

Re: Ownership

Why does the rsync running on the client must be root ? It just has to send the name of the owner of the file to the server which will chown it. I misread it as the receiver at first glance, thus the confusion. You're right that the sender doesn't need to be root. However, this topic split into

  1   2   >