18.3. Services Configuration Tool
/etc/rc.d/init.ddirectory are started at boot time (for runlevels 3, 4, and 5) and which
xinetdservices are enabled. It also allows you to start, stop, and restart SysV services as well as reload
system-config-servicesat a shell prompt (for example, in an XTerm or a GNOME terminal).
Figure 18.1. Services Configuration Tool
/etc/rc.d/init.ddirectory as well as the services controlled by
xinetd. Click on the name of the service from the list on the left-hand side of the application to display a brief description of that service as well as the status of the service. If the service is not an
xinetdservice, the status window shows whether the service is currently running. If the service is controlled by
xinetd, the status window displays the phrase xinetd service.
xinetdservice, the action buttons are disabled because they cannot be started or stopped individually.
xinetdservice by checking or unchecking the checkbox next to the service name, you must select > from the pulldown menu (or the button above the tabs) to reload
xinetdand immediately enable/disable the
xinetdservice that you changed.
xinetdis also configured to remember the setting. You can enable/disable multiple
xinetdservices at a time and save the changes when you are finished.
rsyncto enable it in runlevel 3 and then save the changes. The
rsyncservice is immediately enabled. The next time
rsyncis still enabled.
xinetdis reloaded, and the changes take place immediately. When you save changes to other services, the runlevel is reconfigured, but the changes do not take effect immediately.
xinetdservice to start at boot time for the currently selected runlevel, check the box beside the name of the service in the list. After configuring the runlevel, apply the changes by selecting > from the pulldown menu. The runlevel configuration is changed, but the runlevel is not restarted; thus, the changes do not take place immediately.
httpdservice from checked to unchecked and then select , the runlevel 3 configuration changes so that
httpdis not started at boot time. However, runlevel 3 is not reinitialized, so
httpdis still running. Select one of following options at this point:
- Stop the
httpdservice — Stop the service by selecting it from the list and clicking the button. A message appears stating that the service was stopped successfully.
- Reinitialize the runlevel — Reinitialize the runlevel by going to a shell prompt and typing the command
telinit x(where x is the runlevel number; in this example, 3.). This option is recommended if you change the Start at Boot value of multiple services and want to activate the changes immediately.
- Do nothing else — You do not have to stop the
httpdservice. You can wait until the system is rebooted for the service to stop. The next time the system is booted, the runlevel is initialized without the