Implementation of Wrapper and XINETD (ii) _unix Linux

Editor's note: Wrapper and xinetd are one way to implement Linux access restrictions. We have in the previous article introduced its basic principles and installation of the method of compiling, not see the friends can go to see us today to talk about its configuration. In the following article, we will also detail some examples to facilitate the understanding and mastery.
Reminder: In order to ensure the integrity of the property table, the second page is relatively long, may spend more time downloading, please forgive me.
1. Configuration methods related to the configuration files are as follows:/etc/xinetd.conf/etc/xinetd.d/*                                         //all files in this directory/etc/hosts.allow/etc/hosts.deny   The default configuration file for xinetd is/etc/xinetd.conf. Its syntax and/etc/inetd.conf are completely different and incompatible. It is essentially a combination of/etc/inetd.conf and/etc/hosts.allow,/etc/hosts.deny functions. Each item in the/ETC/XINETD.CONF has the following form:   service Service-name {attribute operator value     ...   Where the service is a required keyword, and the property sheet must be enclosed in curly braces. Each entry defines a service defined by Service-name. Service-name is arbitrary, but is typically a standard network service name, and can also add other non-standard services, as long as they can be activated over a network request, including a network request made by localhost itself. Each service has a number of attributes that can be used, which are described in detail in the table below. The usage rules for the required properties and properties will be described later. The operator can be =,+=, or-=. All properties can use = To assign one or more values, and some properties can be in the form of + = or =, either by adding their value to an existing value table, or by removing its value from the existing value table. Value is the values that are set for the given property.   It needs to be explained that each service can be appended to/etc/xinetd.conf, or separate files can be created in the directory specified in/etc/xinetd.conf, RedHat 7.x recommends the latter approach because of the extensibility , it is more convenient to manage. RedhaT 7.x the default service profile directory is/etc/xinetd.d.