SCO TCP/IP network management --- start of TCP/IP

I have written this article about the management of SCO TCP/IP. I hope it will be helpful to you, just like what was written at the beginning of this topic, this is the basis for hackers, and we still need to discuss it in the direction of network management! Haha!
1 TCP/IP startup
TCP/IP is controlled by the/etc/TCP script file. It is started when you enter the multi-user status and the/etc/tcp file operation content is disabled when you enter the single-user status: it is a script file with the following functions:
Enable or disable TCP/IP by configuring the stream device that is required to support TCP/IP, and enable or disable the daemon related to TCP/IP.
Log On As ROOT and use the command line tcp start or tcp stop to manually START or disable TCP/IP.
This file is linked to files in the etc/rc2.d and/etc/rc0.d directories so that/etc/tcp enters or exits the multi-user status, you can run the START or STOP option. Whether you use Network Confugration Manager to add or delete a Network interface, the ifconfig command will be added or deleted in the script to modify the/etc/tcp file, the/etc/strcf file is also modified. The following describes how the system starts TCP/IP:
. Initializes STREAMS and sockets
. Sets the host name
. Configures Interfaces
. Starts network daemons
. Undoes all of the above on shurdown
/Etc/tcp operation: the configuration supported by the TCP/IP core only needs to be completed once. It mainly includes the STREAMS module stack settings required by TCP/IP.
The system core sets the STREAMS stack at boot. The precondition is that the ksl. disable BOOT string is not required at the BOOT: prompt. When setting the STREAMS stack, the/etc/tcp script file will call the slink command to create the STREAMS stack before any other settings or startup.

Related Articles]

• SCO TCP/IP network management-tool Introduction
  

• SCO TCP/IP network management-daemon)
  

• SCO TCP/IP network management-FTP Configuration