TCP/IP daemons
A subsystem is a daemon, or server, that is controlled by the SRC. A subserver is a daemon that is controlled by a subsystem. (Daemon commands and daemon names are usually denoted by a d at the end of the name.)
The categories of subsystem and subserver are mutually exclusive. That is, daemons are not listed as both a subsystem and as a subserver. The only TCP/IP subsystem that controls other daemons is the inetd daemon. All TCP/IP subservers are also inetd subservers.
The following are TCP/IP daemons controlled by the SRC:
Subsystems
| Item | Description |
|---|---|
| gated | Provides gateway routing functions and supports the Routing Information Protocol (RIP), the Routing Information Protocol Next Generation (RIPng), Exterior Gateway Protocol (EGP), the Border Gateway Protocol (BGP) and BGP4+, the Defense Communications Network Local-Network Protocol (HELLO), Open Shortest Path First (OSPF), Intermediate System to Intermediate System (IS-IS), and Internet Control Message Protocol (ICMP and ICMPv6)/Router Discovery routing protocols. In addition, the gated daemon supports the Simple Network Management Protocol (SNMP). The gated daemon is one of two routing daemons available for routing to network addresses and is the preferred routing daemon. The gated daemon is preferred over the routed daemon because the gated daemon supports more gateway protocols. |
| inetd | Invokes and schedules other daemons when requests for the daemon services are received. This daemon can also start other daemons. The inetd daemon is also known as the super daemon. |
| iptrace | Provides interface-level packet-tracing function for Internet protocols. |
| named | Provides the naming function for the Domain Name Server protocol (DOMAIN). |
| routed | Manages the network routing tables and supports the Routing Information Protocol (RIP). The gated daemon is preferred over the routed daemon because the gated daemon supports more gateway protocols. |
| rwhod | Sends broadcasts to all other hosts every three minutes and stores information about logged-in users and network status. Use the rwhod daemon with extreme care, because it can use significant amounts of machine resources. |
| timed | Provides the time server function. |
Note: Both the routed and gated daemons
are listed as TCP/IP subsystems. Do not run the startsrc
-g tcpip command, which initiates both of these routing
daemons, along with all the other TCP/IP subsystems. Running
both daemons simultaneously on one machine can produce unpredictable
results.
TCP/IP daemons controlled by the inetd subsystem are the following:
inetd Subservers
| Item | Description |
|---|---|
| comsat | Notifies users of incoming mail. |
| fingerd | Provides a status report on all logged-in users and network status at the specified remote host. This daemon uses the Finger protocol. |
| ftpd | Provides the file transfer function for a client process using the File Transfer Protocol (FTP). |
| rexecd | Provides the foreign host server function for the rexec command. |
| rlogind | Provides the remote login facility function for the rlogin command. |
| rshd | Provides the remote command execution server function for the rcp and rsh commands. |
| talkd | Provides the conversation function for the talk command. |
| syslogd | Reads and logs system messages. This daemon is in the Remote Access Service (RAS) group of subsystems. |
| telnetd | Provides the server function for the TELNET protocol. |
| tftpd | Provides the server function for the Trivial File Transfer Protocol (TFTP). |
| uucpd | Handles communications between the Basic Network Utilities (BNU) and TCP/IP. |