You can start services in two ways. First, you can fire up the service when your system boots. In that case, it will occupy its port and wait for incoming connections all the time. However, if you need a service only occasionally, starting it at system boot and keeping it available all the time is a waste of system resources. This is exactly what xinetd is for; the xinetd process listens on behalf of other processes to see whether a connection comes in. If it does, it starts the process, thus making optimal use of system resources. In this chapter, you'll learn how to configure xinetd.
Specifically, I'll cover the following:
• Configuring xinetd with YaST
• Tuning xinetd by hand
• Tuning access to services with TCP Wrapper, a service that you can use to restrict access to services started from xinetd
Was this article helpful?