SUMMARY: Inetd problems.

From: Ian Foster (
Date: Tue Mar 31 1998 - 07:58:31 CST


My problem was that the inetd kept dying for no reason on our SS20 with
256Mb ram running solaris 2.5.1.

The problem hasn't been totally resolved but I was given a temporary fix
to allow telnet users to log in after the inetd stops accepting telnet
connections and this was to use ifconfig to bring the interface down and
then back up which seems to do the trick.

One of the main problems with this was the fact that no core dump was
produced so it made it very difficult to figure out what was going wrong.
Another suggestion was to "truss" the inetd into a file and then I could
see what happened when the inetd died by doind the following:

truss -o <filename> -p <pid of inetd>

another was to run the inetd wit the -t option to enable a trace of who is
connecting to the inetd.

These are both still running at the moment as the inetd has stayed up for
6 days without any problems!

Many thanks to the following from whom I recieved lots of usefull



Ian Foster, Technical support manager, Netkonect Communications Ltd
Tel 01420 542777 Fax 01420 542878 Email
Work Play

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:35 CDT