On 2016-11-14 11:31, Per Jessen wrote:
Per Jessen wrote:
Carlos E. R. wrote:
I read somewhere that this file is been ignored by many daemons.
You're right, in many apps tcp_wrappers is no longer compiled in, but this "hosts deny" directive is part of rsyncd.conf.
Maybe the intention is to use the firewall instead.
Which I will probably do, but it's annoyiung when rsyncd (apparently) has the functionality anyway.
I think I know why "hosts deny" in rsyncd.conf does not work - the incoming connection is handled by xinetd, then passed to rsyncd.
Why don't you run rsyncd as daemon? Maybe it does a difference. Oh, what you say is about the same as I do, it would be xinet which would do the denying.
I thought the problem with inactive clients might be some incompatibility thing between server and client, so I upgraded rsync to the latest (3.1.12), but this made no difference. I am not sure what the "timeout" config option in rsyncd.conf is really meant to do, but it doesn't help in this situation.
Instead, I've written a little wrapper that'll send a SIGALRM to the rsyncd instance after 3 minutes. Admittedly a bit crude, but there is only 40-50M to rsync (which would rarely be upgraded all at once), 3 minutes should be plenty for any client to complete the sync.
Crude :-))) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)