Configuring and Managing MPE/iX Internet Services (August 2002)

Chapter 2
Internet Daemon
Using inetd Message Logging
36
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 INETD.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.
Using inetd Message Logging
There are two kinds of message logging that you, as System Manager, can use to monitor and manage
Internet Services on your system. The first type is event logging, which is always enabled. It records
informational messages, error messages and warnings about the Internet Services. The second type is
connection logging, which you can enable and disable. It records successful and failed connection attempts
and its own status (on or off). Both event logging and connection logging write messages to the $STDLIST
device for inetd and, in some cases, to the system console.
The kinds of informational, error, and warning messages that are always reported for inetd, and what they
mean, are listed in the “Troubleshooting” section, later in this chapter. Connection logging is explained next.
Connection Logging
When connection logging is enabled, the Internet daemon records both successful and failed attempts to
establish a connection with the host system you are managing. Reviewing the log file can give you important
information for managing the Internet Services on your system including:
• Which services are heavily used and which are not.
• Identity of the clients using the Internet Services on your system.
• Pattern of usage, daily, weekly or monthly, for example, for a particular service or set of services.
• Which host(s) are being used for unsuccessful connection attempts, which can indicate who may be
attempting to access to your system without authorization.