Anton Aylward wrote:
On 11/14/2016 07:44 AM, Per Jessen wrote:
Anton Aylward wrote:
On 11/14/2016 02:17 AM, Per Jessen wrote:
[...] Running rsyncd with xinetd allows the system to do a lot more work.
Do you mean 'requires', as in 'do work that alternatives might not require and so places a greater load on the system" or do you mean "offers more options and flexibility" ??
xinetd has a higher listen backlog than rsyncd (3.0.7), that's all.
By "backlog" I presume you mean connection requests that have not yet spawned a server to deal with the it".
It's the "backlog" parameter of the listen() call, see "man listen": "The backlog argument defines the maximum length to which the queue of pending connections".
[...]
Yes, that is possible, but the main issue is one of apparently inactive clients just hanging around clogging up the system.
Are these clients that have completed the job?
No, they look like they never get started. I've straced a few and they run a select() with a 60s timeout, it times out a number of times and then eventually something happens and the process exist. I've seen processes in this state for 15mins and 30mins and longer.
Hmm. I take it that you don't really mean 'clients', but instances of the spawned rsyncd. To me, 'clients' are the other end of the connection, the requesters not the servitors.
Well, the server process is active just waiting for client side to do something. -- Per Jessen, Zürich (3.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org