Regression in rsync since the glibc 2.32 update (including the 2.33 update too)
by tadgy from LinuxQuestions.org on (#5EGVT)
There is a regression in rsync since version 3.2.3 tag -2 (including the post mass rebuild for glibc 2.33 version with the -3 tag) which prevents the setting of permissions when /proc is not available - which occurs when using the option:
Code:use chroot = true(or leaving it unset since true is the default)
To demonstrate, just create a rsync daemon process that utilises "use chroot" option and try to upload a file to a repository - it produces the error:
Code:Operation not supportedThis is apparently due to glibc implementing lchmod() in a less than perfect way as discussed here: https://github.com/WayneD/rsync/issues/109 and in various distributions specific bugtrackers.
The solution, as detailed in the above link, is to patch rsync to not detect the lchmod() call on Linux hosts - there is already a commit in git to implement this.
I've had to revert the rsync package on slackware.uk to the (pre glibc 2.32) version ending with the -1 tag, which is unaffected.
Hope this can get fixed ASAP :)
Code:use chroot = true(or leaving it unset since true is the default)
To demonstrate, just create a rsync daemon process that utilises "use chroot" option and try to upload a file to a repository - it produces the error:
Code:Operation not supportedThis is apparently due to glibc implementing lchmod() in a less than perfect way as discussed here: https://github.com/WayneD/rsync/issues/109 and in various distributions specific bugtrackers.
The solution, as detailed in the above link, is to patch rsync to not detect the lchmod() call on Linux hosts - there is already a commit in git to implement this.
I've had to revert the rsync package on slackware.uk to the (pre glibc 2.32) version ending with the -1 tag, which is unaffected.
Hope this can get fixed ASAP :)