This doesn't seem right to me. Changed the path = Bin and the call to rsync to use the -R option which I think is to use relative path. Still fails on chroot but the rsyncd.log has the following;
2020/07/29 08:52:17 [10277] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/29 08:52:17 [10277] rsync: [Receiver] chroot /Bin failed: No such file or directory (2) The error message is correct there is no /Bin directory but the path statement indicates Bin as a relative path (ensure the test script running from /home/cliff and there is a Bin directory there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
