Anton Aylward wrote:
On 11/13/2016 12:48 PM, Per Jessen wrote:
I'm running rsyncd via xinetd.
I've long ago discontinued the use of xinetd.
Ditto, but in this case xinetd works better than rsyncd. My rsyncd on this box is a little old, so does not support the "listen backlog" cofig directive. Running rsyncd with xinetd allows the system to do a lot more work.
Remember, you can run Xinetd in debug mode to find out in more detail what's going on.
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.
===============
You don't mention what version of the OS you are using.
Backlevel as usual. 11.4 I think.
If it is a later model, you may find it more manageable to use a systemd unit rather than a an Xinetd descriptor.
Why? Well in one sense systemd is already doing what inetd & xinetd did, it listens on a whole bunch of sockets for requests and then fires up services.
When I upgrade or move this service, I expect to just revert to rsyncd. Both xinetd and systemd are superfluous in this scenario. -- Per Jessen, Zürich (1.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org