12.07.2015 Views

Red Hat Enterprise Linux 5 Administration Unleashed

Red Hat Enterprise Linux 5 Administration Unleashed

Red Hat Enterprise Linux 5 Administration Unleashed

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The xinetd Super Server 381LISTING 19.1v6onlyContinued= no# setup environmental attributes## passenv =groups= yesumask = 002# Generally, banners are not used. This sets up their global defaults## banner =# banner_fail =# banner_success =}includedir /etc/xinetd.dNOTEEach of the attributes in Listing 19.1 is explained in the following text. However, noticethat some are commented out by default because setting them to a blank value hasmeaning.The first two options inside the default section of xinetd.conf are enabled and disabled.Enabling and disabling xinetd services should be done in the individual services files inthe /etc/xinetd.d/ directory with the disable attribute set to yes or no as described inthe next section “Individual xinetd Service Files.” Using the enabled and disabledoptions in xinetd.conf is only recommended for temporary situations such as testing orif you think your system has been compromised and need to turn off all the unnecessaryservices. To use one or both of these attributes, uncomment one or both of them first.The enabled option can be used to list services that are allowed to accept connections.The services listed with this option still need to be enabled in their individual servicesfiles in /etc/xinetd.d/ by setting the disable attribute to no and making sure theDISABLE flag is not listed in the flags attribute. If the disabled option is not set, only thexinetd services in the enabled list are allowed to accept connections.19If the disabled option is set, only the xinetd services in the enabled list accept connectionsunless they are also in the disabled list. All services listed with the disabled optionare not allowed to accept connection requests.Both attributes accept a space-separated list of service IDs. For both these options, theservice ID must be used, not the service name. In the individual service files in/etc/xinetd.d/, the id attribute sets the service ID to a unique identifier. If an ID is notgiven, the ID defaults to the service name. Most service IDs are the same as the service

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!