Xinetd.conf file

It also provides service-specific configuration options for access control, enhanced logging, binding, redirection, and resource utilization control. When a client host attempts to connect to a network service controlled by xinetd , the super service receives the request and checks for any TCP wrappers access control rules.

You can also specify a custom log file for xinetd using the -filelog as shown below. Using -limit option, you can also limit the number of concurrent process that can be running.

This helps xinted to avoid process table over-flow. The following example will perform xinted internal state consistency check every two minutes seconds as specified in the -cc option. However, the english version is more up to date.

We appreciate your interest in having Red Hat content localized to your language. Please note that excessive use of this feature could cause delays in getting specific content you are interested in translated.

We are generating a machine translation for this content. Depending on the length of the content, this process could take a while. If this attribute is not defined, the default protocol employed by the service will be used. If its value is yes , the service is single-threaded; this means that xinetd will start the server and then it will stop handling requests for the service until the server dies and that the server software will accept the connection.

If the attribute value is no , the service is multi-threaded and xinetd will keep handling new service requests and xinetd will accept the connection. The user attribute can either be numeric or a name.

This attribute is ineffective if the effective user ID of xinetd is not super-user. The group attribute can either be numeric or a name. This attribute is ineffective if the effective user ID of xinetd is not super-user and if the groups attribute is not set to 'yes'. Its value is a possibly negative number; check nice 3 for more information.

This attribute is only valid if xinetd has been configured with the libwrap option. If the rightmost components are 0, they are treated as wildcards for example, IPv6 hosts may be specified in the form of abcd:ef The rightmost rule for IPv4 addresses does not apply to IPv6 addresses. There is no need for all 4 components i. However, the factorized part must be at the end of the address. This form does not work for IPv6 hosts. When a connection is made to xinetd, a reverse lookup is performed, and the canonical name returned is compared to the specified host name.

You may also use domain names in the form of. If the reverse lookup of the client's IP is within. Specifying this attribute without a value makes the service available to nobody.

These two attributes determine the location access control enforced by xinetd. If none of the two is specified for a service, the service is available to anyone.

An interval has the form hour:min-hour:min connections will be accepted at the bounds of an interval. Hours can range from 0 to 23 and minutes from 0 to Possible facility names include: daemon, auth, authpriv, user, mail, lpr, news, uucp, ftp local Possible level names include: emerg, alert, crit, err, warning, notice, info, debug.

If a level is not present, the messages will be recorded at the info level. Two limits on the size of the log file can be optionally specified. The first limit is a soft one; xinetd will log a message the first time this limit is exceeded if xinetd logs to syslog, the message will be sent at the alert priority level.