syncfiles builds an xdcp subrequest with no username. xdcp takes its user from
-l, then from DSH_FROM_USERID, and otherwise leaves it unset, so the sync ends
up running as whatever identity xcatd happens to have rather than one the
request states.
That gap dates from 2c9bdf848, which removed the forceroot flag because any
caller could set it, and replaced it by passing the real username through.
updatenode was updated to do that; syncfiles was not. Its request comes from the
node, so there is no calling user to carry through, and root is what the sync
has to run as.
Name it explicitly, the same way updatenode does. This is a consistency and
hardening change: on a management node running as root the resulting identity is
the same either way, and no behavior difference is observable today.
Co-authored-by: Jarrod Johnson <10814490+jjohnson42@users.noreply.github.com>
* add support for syncfiles with scp
* refine logic of EXECTUTE support message non rsync filesync
* refine syncfiles
* add startsyncfile script for cumulus
* refine format, fix updatenode without options causes command to crash #5142
Vinícius Ferrão
GONG Jie
yangsong
Mark Gurevich
lissav
bp-sawyers
jbjohnso
daniceexi