Ah, thanks - adding --super appears to have resolved the problem. Ran
another full of the test system, and backuppcfs now shows correct file
ownerships.
I'm still missing --protect-args, --delete-excluded, and --partial from
the defaults, so I'll probably also add those after checking the man
page to see what they do. (...and also missing --one-file-system, but
that's deliberate.)
For the record, my original settings were:
$Conf{RsyncArgs} = [
'--numeric-ids',
'--perms',
'--owner',
'--group',
'-D',
'--links',
'--hard-links',
'--times',
'--block-size=2048',
'--recursive',
'--delete'
];
It's not something I would have been likely to modify manually (aside
from removing --one-file-system), but I don't recall whether the base
settings were migrated from my original test install (which was BPC3) or
if Debian chose a different set of default settings than upstream.
On 11/18/22 19:31, Kris Lou via BackupPC-users wrote:
Look again at your RsyncArgs, they don't match the defaults [1],
though obviously your system may justify it:
-o, --owner
This option causes rsync to set the owner of the destination file
to be
the same as the source file, but only if the receiving rsync is
being run
as the super-user (see also the --super and --fake-super options).
Without
this option, the owner of new and/or transferred files are set to
the invoking
user on the receiving side...
-g, --group
This option causes rsync to set the group of the destination file
to be the same as
the source file. If the receiving program is not running as the
super-user (or if
--no-super was specified), only groups that the invoking user on
the receiving side
is a member of will be preserved. Without this option, the group
is set to the default
group of the invoking user on the receiving side...
And correspondingly:
--super
This tells the receiving side to attempt super-user activities
even if the receiving rsync wasn't
run by the super-user. These activities include: preserving
users via the --owner option,
preserving all groups(not just the current user's groups) via
the --groups option, and copying
devices via the --devices option. This is useful for systems
that allow such activities without being
the super-user, and also for ensuring that you will get errors
if the receiving side isn't
being run as the super-user.
To turn off super-user activities, the super-user can use
--no-super.
Defaults are (--one-file-system is often overlooked):
$Conf{RsyncArgs} = [
'--super',
'--recursive',
'--protect-args',
'--numeric-ids',
'--perms',
'--owner',
'--group',
'-D',
'--times',
'--links',
'--hard-links',
'--delete',
'--delete-excluded',
'--one-file-system',
'--partial',
'--log-format=log: %o %i %B %8U,%8G %9l %f%L',
'--stats',
#
# Add additional arguments here, for example --acls or --xattrs
# if all the clients support them.
#
#'--acls',
#'--xattrs',
];
[1]
https://github.com/backuppc/backuppc/blob/174e707c0f64d9fe6eb699612be35fa214cafc3f/conf/config.pl#L1276-L1300
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
