https://bugzilla.samba.org/show_bug.cgi?id=13463
--- Comment #5 from Simon Deziel ---
The `Restart=on-failure` option was added in
https://github.com/WayneD/rsync/commit/d41bb98c09bf0b999c4eee4e2125c7e5d0747ec4
This should paper over the problem of late showing IPv6 addresses due to DAD
taking t
https://bugzilla.samba.org/show_bug.cgi?id=13463
--- Comment #4 from Simon Deziel ---
Since rsyncd exits with error code 10 ("Error in socket I/O") there are two
possible ways to improve the systemd unit:
[Service]
...
RestartForceExitStatus=10
Or:
[Service]
...
Restart=on-failure
Both shoul
https://bugzilla.samba.org/show_bug.cgi?id=13463
--- Comment #3 from Andreas Hasenack ---
Thanks for all the opinions. I have one remaining issue, and that is with
"systemctl start rsync.service" not detecting the failure right away.
The systemd unit file calls rsync like this:
[Service]
ExecSt
https://bugzilla.samba.org/show_bug.cgi?id=13463
--- Comment #2 from Kevin Korb ---
I agree with Carson. If rsync is told to do the impossible it should fail with
an appropriate error and exit code.
Unfortunately I would also have to argue that the current behaviour is wrong
because it does not
https://bugzilla.samba.org/show_bug.cgi?id=13463
--- Comment #1 from Carson Gaspar ---
If this is done, please make it optional. I want my daemon to break when given
an invalid config, e.g. a typo'd IP address. The fact that systemd folks are
crazy and people don't want to have proper startup dep
https://bugzilla.samba.org/show_bug.cgi?id=13463
Bug ID: 13463
Summary: Please consider using the IP_FREEBIND socket option
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity
Hi All,
This is my first mail on this list.
I have to use rsync on windows system and want to know if the socket option
can be used as on Linux system.
Otherwise, is there someone who has tried to use rsync daemon with more than
200 concurrent connexion. Is there any tweaking I can do to help
