Running the Internet daemons

If a host is a server, it invokes the appropriate daemon to satisfy a client's requests. A TCP/IP server typically runs the inetd daemon, also known as the Internet super-server.

You can start inetd in your machine's rc.local file; see the description of /etc/rc.d/rc.sysinit in the Controlling How Neutrino Starts chapter in this guide.

Running inetd lets outside users try to connect to your machine and thus is a potential security issue if you don't configure it properly.

The inetd daemon listens for connections on some well-known ports, as defined in /etc/inetd.conf, in the TCP/IP network. On receiving a request, it runs the corresponding server daemon. For example, if a client requests a remote login by invoking rlogin, then inetd starts rlogind (remote login daemon) to satisfy the request. In most instances, responses to client requests are handled this way.

You use the super-server configuration file /etc/inetd.conf to specify the daemons that inetd can start.

Note: As shipped in the Neutrino distribution, the file contains commented-out descriptions of all currently shipped Neutrino TCP/IP daemons and some nonstandard pidin services. You need to edit inetd.conf and uncomment the descriptions of the ones you want to use.

When it starts, inetd reads its configuration information from this configuration file. It includes these commonly used daemons:

File transfer.
Remote login.
Remote shell.
Remote terminal session.
DARPA trivial file transfer.

You may also find other resident daemons that can run independently of inetd—see the Utilities Reference for descriptions:

Internet boot protocol server.
Dynamic Host Configuration Protocol daemon.
Line printer daemon.
Distance-Vector Multicast Routing Protocol (DVMRP) daemon.
Internet domain name server
Network Time Protocol daemon.
RIP and RIPv2 routing protocol daemon
System status database.
SNMP agent.
NFS server.

These daemons listen on their own TCP ports and manage their own transactions. They usually start when the computer boots and then run continuously, although to conserve system resources, you can have inetd start bootpd only when a boot request arrives.