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#36069 - [rsync] rsyncd.socket to refuses connections but rsyncd.service works as expected
Attached to Project:
Arch Linux
Opened by John (graysky) - Monday, 08 July 2013, 07:47 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 18 October 2015, 21:46 GMT
Opened by John (graysky) - Monday, 08 July 2013, 07:47 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 18 October 2015, 21:46 GMT
|
DetailsDescription:
I am running rsyncd.service on my nas via the included rsyncd.service successfully. I'd like to use rsyncd.socket instead of the service but found that simply starting the socket does not allow connections. Attempted connection while rsyncd.socket is active: % rsync nas::share rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(764) [Receiver=3.0.9] I found this slightly older thread that states that one needs to copy /usr/lib/systemd/system/rsyncd@.service to /etc/systemd/system and edit the 'User=' and 'Group=' vars to match the desired ones for socket activation to properly work[1]. I did this changing the two vars to the user/group I defined in /etc/rsyncd.conf but again, am unable to connect. Is this a problem with the package or with my configuration? Attempted connection with the modified file while rsyncd.socket is active: % rsync nas::share rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(764) [Receiver=3.0.9] 1. https://bbs.archlinux.org/viewtopic.php?id=154905 Steps to reproduce: 1) Have a functional rsyncd with the service. 2) Stop the service. 3) Start the socket. 4) Attempt to connect --> this should fail. 5) cp /usr/lib/systemd/system/rsyncd@.service /etc/systemd/system 6) Edit the /etc/systemd/system/rsyncd@.service defining the User= and Group= to match the conf file. 7) Stop the socket. 8) systemctl --system daemon-reload 9) Start the socket. 10) Attempt to connect --> this should fail. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 18 October 2015, 21:46 GMT
Reason for closing: None
Additional comments about closing: User requested
Sunday, 18 October 2015, 21:46 GMT
Reason for closing: None
Additional comments about closing: User requested
rsyncd.conf
This is probably not a packaging bug.
Pierre, if you're confident that this isn't/wasn't a packaging bug, I'd say go ahead and close it.