rsync - Management of UIDs and GIDs when reserved on a Remote system

[Kevin Korb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No, rsync would store the files with the numeric UID and GID as is on
the source without regard to the existence or non-existence of a
matching account.  This could mean that ls would show numbers in those
columns, or incorrect names in those columns, or (perhaps by
coincidence) show the correct names in those columns.  The important
thing is that if you backup and restore with --numeric-ids you will
get back what you started with regardless of what the backup system
thinks about the data.

On 05/18/2015 09:16 PM, Michael wrote:
> Kevin Korb <kmk <at> sanitarium.net> writes:
>> 
>> 3) --numeric-ids copies both as the number.  This is what you
>> normally want for backups.  This way you have the exact UID and
>> GID stored on the backups regardless of what those numbers mean
>> to the backup system.  Just remember to use --numeric-ids when
>> you restore.  This is especially important if you have to restore
>> from a live environment that has completely different UIDs and
>> GIDs than your normal system. That environment would have no idea
>> how to translate names from option #2 during a restore.
> 
> Hi Kevin,
> 
> Regarding the option --numeric-ids, how would rsync manage the
> situation where the UID and GID(s), of a file being copied to a
> Remote system, have been reserved on the Remote system. Does rsync
> search for and allocate the next available IDs?
> 
> Thanks, Michael.
> 
> 
> 

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlVakU4ACgkQVKC1jlbQAQe6AACcDo7ecpCTUgDJkxBlx05OJ57D
pf8AniaeelYUKcJDl+Zl/xjGcYkcmjOW
=nRGQ
-----END PGP SIGNATURE-----