|
|
Configuring and Managing MPE/iX Internet Services: HP 3000 MPE/iX Computer Systems > Chapter 2 Internet DaemonStarting and Stopping inetd |
|
On the HP 3000, the instructions for starting the Internet daemon are contained in the job file JINETD.NET.SYS. When you stream JINETD, it invokes the daemon and reads the inetd configuration file to determine what services have been configured, and listens for connection requests for those services. Any messages relating to inetd are sent either to the console or to $STDLIST for JINETD, which is a spool file. The Internet daemon will continue to run, responding to requests for any of the configured services, until you stop it. The Internet daemon only terminates in an error state if there are no valid services listed in the configuration file. To start inetd, you stream the JINETD job. You may do this manually, by entering the STREAM command when the system is running, or you may include the STREAM JINETD command in the SYSSTART file to have inetd automatically started at system startup. If you attempt to start inetd when it is already running, you'll see the following error message and the job will not be started: An inetd is already running. If you want to have the Internet daemon started automatically when your system starts up, add the STREAM JINETD command to the SYSSTART file. When you do, be sure that the stream command follows the network startup command NETCONTROL START. When you stream the job file JINETD.NET.SYS, it logs on as MANAGER.SYS. As part of the installation of inetd, you must take care of any password requirements for this job. Two of the ways that you can do this include:
You may also start inetd interactively, though this is not recommended for normal use. To do so, enter the following command at the CI prompt: :INETD.NET.SYS Or, from the POSIX shell enter this command: $/etc/inetd When you start inetd interactively, $STDLIST for the Internet daemon is your terminal. This means that all error and warning messages that normally go to JINETD's spool file will appear on the screen. While inetd is running, any errors and other status messages that it generates are recorded so that you can monitor its condition. All errors, regardless of their degree of seriousness, are sent to the $STDLIST device assigned to inetd. For example, if you streamed JINETD, error messages will appear in the spool file associated with that job. More critical errors are displayed on the system console in addition to being sent to $STDLIST. For more information, read "Using inetd Message Logging" later in this chapter. To stop inetd, you abort the JINETD job. Stopping the inetd server (aborting JINETD) will cause subsequent incoming connection requests to be refused.
There are three options that you may add to the command line when you enter INETD.NET.SYS at the MPE CI prompt or enter /etc/inetd from the POSIX shell.
|
|