| /etc/inetd.cnf: Unusable configuration file | The Internet daemon cannot
access its configuration. The error message preceding this one specifies
the reason for the failure. |
| /etc/inetd.conf: line number: nnn error | There is an error on the line
specified by nnn in the inetd configuration file. The Internet daemon skips
this line, continues reading the rest of the file, and configures
itself accordingly. To solve the problem, open the configuration
file, edit the erroneous line, and save the corrected version. Then,
tell inetd to reread the new version of INTEDCNF by issuing the inetd.net.sys -c command at the CI prompt. |
| system call:... | The system call noted in the error
message failed. See the corresponding entry in the Berkeley
Sockets/iX Reference Manual for a description of the
system call. The reason for the failure is explained in the error message
appended to the system call name. |
| Cannot configure inetd | Due to errors in the inetd configuration file, none of the services it lists could
be set up properly. |
| Too many services running | The maximum number of services
allowed to access inetd simultaneously has been exceeded. |
| file: found before end of the line | An entry in a configuration file
may need to exceed one line. If so, you indicate that the line continues
by inserting a backslash at the end, then continue typing data on
the next line. If, however, you place a backslash in the middle
of the line, inetd will ignore it and continue reading to the end
of the current line, but will not continue to the next line. In
this case, it is likely that the configuration information will
be misread. |
| service/protocol; Unknown service | The system call getservbyname failed because the service is not listed in the
services file. To solve the problem, you may either add an entry
for the service to the services file or delete the entry for the
service from the inetd configuration file. |
| service/protocol: Server failing (looping), service terminated. | When inetd tries to start 40 servers within 60 seconds
for a datagram service, it assumes that the server is failing to
handle the connection. To avoid entering a potentially infinite
loop, inetd issues this message, discards the packet requesting
the socket connection, and refuses further connections for this
service. After 10 minutes, inetd tries to reinstate the service and accept connection
requests. |
| service/protocol: socketservice/protocol: listenservice/protocol: getsockname | Any of these three errors renders
the service unusable. To make the service available again, you must
issue the inetd -c command to have inetd reread the configuration file. |
| service/protocol: bind:... | Indicates that the service is
temporarily unusable because inetd cannot bind the service to the socket. After 10
minutes, inetd tries to bind the socket again. If it is successful,
then it will listen for a connection request and provide the appropriate
service. If it fails, it will wait another 10 minutes and try again. |
| service/protocol: Access denied to remote host (address) | The remote host failed to pass
the security test for the service indicated in the message. If this
message appears frequently, it can indicate that someone is trying
to repeatedly access your system, and failing. |
| service/protocol: Connection from remote host (address) | When connection logging is enabled,
this message indicates a successful connection attempt to the specified
service. |
| service/protocol: Added service, server executable | Records the services that are
added when you reconfigure inetd. |
| service/protocol: New... | Lists the new user identifications,
new servers, or executable programs used for the service when reconfiguring inetd. |
| service/protocol: Deleted service | Records the services that are deleted when
you reconfigure inetd. |
Printable version
