HP 3000 Manuals HP 3000 Manuals
Starting 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.
Starting inetd from a job
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.
To start inetd manually:
1. Log onto your system as MANAGER.SYS,NET.
2. Check to make sure that inetd has not already been started by
entering at the CI prompt:
:SHOWJOB JOB=@J
Look for the job logged on as JINETD.NET.SYS and, if it is not
listed, continue with the next step.
3. At the CI prompt, enter STREAM JINETD.NET.SYS.
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.
Starting JINETD automatically
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.
A note about passwords on JINETD
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:
* Add the MANAGER.SYS passwords directly to the job file, then alter
the file security afterwards so that only MANAGER.SYS can read it.
For example:
:ALTSEC JINETD.NET.SYS; (R,W:CR;E,L:AC)
* Use the PASSEXEMPT parameter of the JOBSECURITY command (version
C.55.00 and later) to control password exemption.
Starting inetd interactively
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.
Error and status reporting for inetd
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.
Stopping inetd
To stop inetd, you abort the JINETD job. Stopping the inetd server
(aborting JINETD) will close an open connections on any of the currently
running Internet Services. Also, any subsequent incoming connection
requests are refused.
1. First find the number assigned to JINETD by entering:
:SHOWJOB JOB=@J
You will see a display of job information similar to the figure
below.
________________________________________________________________________________
| |
| |
| JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME |
| |
| #J6546 EXEC 10S LP THU 12:42A TRNSPOOL,MGR.NSD |
| #J6539 EXEC 10S PP THU 12:32A SPOOLJ,UNISPOOL.SYS |
| #J6540 EXEC 10S LP THU 12:41A JINETD.NET.SYS |
| |
| 3 JOBS (DISPLAYED): |
| 0 INTRO |
| 0 WAIT; INCL 0 DEFERRED |
| 3 EXEC; INCL 0 SESSIONS |
| 0 SUSP |
| JOBFENCE= 6; JLIMIT= 10; SLIMIT= 60 |
| |
| |
| CURRENT: 1/15/96 16:12 |
| |
| JOBNUM STATE IPRI JIN JLIST SCHEDULED-INTRO JOB NAME |
| |
| #J6667 SCHED 15 10S PP 1/15/96 16:50 CHECKJOB,MANAGER.SYS |
| |
| 1 SCHEDULED JOB(S) |
| |
________________________________________________________________________________
2. Issue the ABORTJOB command, specifying JINETD's job number on the
command line. For example, if JINETD were logged on as job number
"6540", you would enter:
:ABORTJOB #J6540
NOTE If you have started inetd interactively, you use the -k option to
kill (stop) it. To do so, enter INETD.NET.SYS -k at the CI prompt
or enter /etc/inetd -k from the POSIX shell.
Summary of inetd command line options
There are three options that you may add to the command line when you
enter JINETD.NET.SYS at the MPE CI prompt or enter /etc/inetd from the
POSIX shell.
-c Instructs inetd to reread the configuration file.
Use this after you have made changes to the
configuration (such as adding a new service) that
you want to put into effect now, for an executing
inetd.
-k Kills, or stops, the currently executing inetd.
-l A toggle command that starts or stops connection
logging for inetd.