Solutions Log » xinetd http://solutions.unixsherpa.com by Dan Reiland Tue, 05 Apr 2011 16:42:14 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 xinetd per_source limit issueshttp://solutions.unixsherpa.com/2010/02/09/xinetd-per_source-limit-issues/ http://solutions.unixsherpa.com/2010/02/09/xinetd-per_source-limit-issues/#comments Tue, 09 Feb 2010 09:32:34 +0000 Dan http://solutions.unixsherpa.com/?p=241 Issue:
Users note availability issues when accessing services backed by xinetd (subversion, rsync, etc.)

Identification:
Syslog on the affected server will present multiple lines containing daemon per_source_limit for 0.0.0.0.

Cause:
You have exceeded per_source_limit defaults imposed by your xinetd configuration. Many distributions include per_source limits that may not be suitable for your use case. Evaluate your needs carefully.

Resolution:
Modify the default setting for per_source in /etc/xinetd.conf or modify the service specific configuration (recommended) under /etc/xinet.d. per_source limits may be set as follows:

per_source = 10

per_source may be set to an integer or UNLIMITED (the number represents the number of connections allowed per host). A sensible fixed value is always better than UNLIMITED.

Reference: xinetd.conf(5)

]]> http://solutions.unixsherpa.com/2010/02/09/xinetd-per_source-limit-issues/feed/ 0