Per former comments marking as fixed and adding Xenial task. It is still an issue in Xenial, but since no one here was participating I wonder about the severity.
Also we would certainly not backport the fix that was taken. I filtered it a bit and it looks like http://paste.ubuntu.com/p/TNvQpqbNRb/ So with that you still won't be able to get it through /etc/default/rsyncd. All you'd find is a comment in there how to do it now. Marking it low due to that ** Also affects: rsync (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released ** Changed in: rsync (Ubuntu Xenial) Status: New => Triaged ** Changed in: rsync (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1707136 Title: ryncd does not start when RSYNC_ENABLE is specified Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Triaged Status in rsync package in Debian: Fix Released Bug description: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1707136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp