On 2016-11-14 13:29, Anton Aylward wrote:
On 11/14/2016 02:17 AM, Per Jessen wrote:
Afaict, xinetd is not part of the problem. xinetd just forks rsyncd for every new connection, and I would expect rsyncd to deny clients matching my "hosts deny" setting from rsyncd.conf.
I'm leaning to the belief that Xinetd *is* the problem becuase it is Xinetd that sees the connection information and should be handling the allow/deny, and that the relevant information is lost by the time rsyncd gets the connection.
Yep. But... I see the advantage of xinetd when the target service is used sparsely. Once the job is finished, the rsyncd daemon exits and frees resources. But if it is used regularly, why not use the rsync daemon directly? Another thing that I do not know, is what happens when there are two or more clients simultaneously. Do you get as many daemons running? In that case, you start to lose the advantage. Me, I also have rsynd via xinetd. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)