TCP/IP Services

Services such as telnet, ftp, and rlogin are started by the inetd daemon,
which runs automatically at boot time. Like the name service ordering
specified in nsswitch.conf, you can configure TCP/IP services in the file
/etc/inetd.conf by using the inetd -t flag.

For example, you can use inetd to log the IP addresses of all incoming
TCP connections (remote logins and telnet). To turn the logging on, kill
the running inetd and type:

# /usr/sbin/inetd -t -s

The t switch turns on TCP connection-tracing in inetd. Refer to the

inetd(1M) and inetd.conf(4) man pages.

The Boot Process

The following information is provided for your reference. It is a brief

overview of the network booting processes to help you better visualize
what is happening during configuration.

Note - The names of startup scripts might change from one release to
another.

1. You start the operating system on a host.

2. The kernel runs /sbin/init, as part of the booting process.
3. /sbin/init runs the /etc/rcS.d/S30rootusr.sh. startup script.
4. The script runs a number of system startup tasks, including
establishing the minimum host and network configurations for
diskless and dataless operations. /etc/rcS.d/S30rootusr.sh
also mounts the /usr file system.
1. If the local database files contain the required configuration
information (host name and IP address), the script uses it.
2. If the information is not available in local host
configuration files, /etc/rcS.d/S30rootusr.sh uses
RARP to acquire the host's IP address.
5. If the local files contain domain name, host name, and default
router address, the machine uses them. If the configuration
information is not in local files, then the system uses the
Bootparams protocol to acquire the host name, domain name, and
default router address. Note that the required information must be
available on a network configuration server that is located on the
same network as the host. This is necessary because no
internetwork communications exist at this point.
6. After /etc/rcS/S30rootusr.sh completes its tasks and several
other boot procedures have executed, /etc/rc2.d/S69inet runs.
This script executes startup tasks that must be completed before the
name services (NIS, NIS+, or DNS) can start. These tasks include
configuring the IP routing and setting the domain name.
7. At completion of the S69inet tasks, /etc/rc2.d/S71rpc runs.
This script starts the NIS, NIS+, or DNS name service.
8. After /etc/rc2.d/S71 runs, /etc/rc2.d/S72inetsvc runs. This
script starts up services that depend on the presence of the name
services. S72inetsvc also starts the daemon inetd, which manages
user services such as telnet.