Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30095 - [rsync] add systemd service file
Attached to Project:
Arch Linux
Opened by Marius (65kid) - Friday, 01 June 2012, 11:07 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 07 June 2012, 06:29 GMT
Opened by Marius (65kid) - Friday, 01 June 2012, 11:07 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 07 June 2012, 06:29 GMT
|
DetailsPlease add the attached systemd service file to the rsync package.
no response upstream: https://bugzilla.samba.org/show_bug.cgi?id=8416 there is a small problem with this service file: when the service is stopped by systemd with SIGTERM, rsync returns a non-zero exit code. Therefore systemd considers the service failed after it has been stopped. I filed a bug about this upstream: https://bugzilla.samba.org/show_bug.cgi?id=8967 I'm sure this can be worked around somehow in the service file, but IMHO this is not a real problem and we should just wait for upstream to fix this. Other opinions welcome... 
rsyncd.service
(0.1 KiB)
|
This task depends upon
But in this case the service will never be considered "failed", even if it actually does (for whatever reason).