+++ This bug was initially created as a clone of Bug #1018520 +++
> Description of problem: The systemd rsyncd.socket unit does not work. It says "Accept=yes".
> According to "man systemd.socket", when Accept is set to yes,
> there must be an accompanying rsyncd@.service file. But there is no such file
> in the rpm. Instead, we have rsyncd.service, which works fine on a standalone
> basis without using the rsyncd.socket unit. But it would be nice if
> rsyncd.socket were to work so I wouldn't need to leave the rsyncd server
> running all the time.
Version-Release number of selected component (if applicable):
--- Additional comment from Jef Spaleta on 2013-12-29 14:34:13 EST ---
> I've heard reports that rsyncd.socket isn't working in F20.
Yes, it's still broken. Same fix as for F19 needs to be applied.
Thank you for heads-up. The same fix was applied in F20, but unfortunately the bodhi update system seems to have difficulties with preparing update from this F20 build. As a workaround solution you can use koji build from http://koji.fedoraproject.org/koji/buildinfo?buildID=472656 .
I am sorry for any inconveniences.
rsync-3.1.0-2.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rsync-3.1.0-2.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
rsync-3.1.0-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.