Oh, yeah. Well, "it depends". If the two machines in question share
the same directory service, then I might want rsync to refuse to
create an ACE with an invalid UUID. If, OTOH, I'm backing up my home
directory to another machine on my network and the two machines do not
share a Directo
On Tue, 2009-09-01 at 09:09 -0500, Mike Bombich wrote:
> Rsync shouldn't be converting UUID to uid/gid *for ACL entries*
> (because Mac OS X stores those ACEs with a reference to a UUID, not a
> uid/gid). For file ownership, etc., it should maintain its current
> behavior.
My point is that
Rsync shouldn't be converting UUID to uid/gid *for ACL entries*
(because Mac OS X stores those ACEs with a reference to a UUID, not a
uid/gid). For file ownership, etc., it should maintain its current
behavior.
On Aug 31, 2009, at 10:08 PM, Matt McCutchen wrote:
On Mon, 2009-08-31 at 16:
On Mon, 2009-08-31 at 16:59 -0500, Mike Bombich wrote:
> Regardless, rsync shouldn't be converting uuid to uid/gid for Mac OS
> X, it's unnecessary.
This is really a question of whether Mac users expect users/groups to be
preserved by uid/gid or by uuid. Are you saying it makes more sense to
pr
That error occurs when rsync tries to set an ACE specifying a user
that does not exist. Here's what happens:
1) Read ACE on source file --> on Mac OS X, the user or group of the
ACE is stored using the user or group's UUID
2) Convert UUID to uid/gid using mbr_uuid_to_id, also store which typ
Hi,
Since upgrading to Snow Leopard, my backup script throws an error msg :
rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
This happened both with 3.0.5 and 3.0.6 that I just installed.
Can someone tell me what it means ? I have no clue on what/where to
look for.
Thanks
Al
