>One of our servers a 2100 4/200 had been up for over 5 months
>without a reboot. About 2 weeks ago the inetd process stopped
>running which prevented any incoming telnet sessions from being
>creating. The inetd process was re-started manually and all was
>fine. Yesterday the same thing occurred. This time a re-boot
>was done and all is fine now.
>
>Anyone familiar with this behavior?
>
>This server is running 4.0a. The only patch applied to it
>is the infamous ping patch.
The consensus seems to be that this is caused by over committed swap
mode with the result being running out of swap space. Inetd is
the process that gets zapped as a result.
___________________________________________________________________
Karen Y. Byrd C511 Richards Bldg.
Systems Manager 3700 Hamilton Wlk.
Univ. of Pa. Philadelphia, PA 19104-6062
School of Medicine Voice: 215/898-6865
Med. Sch. Computer Facility/ Fax: 215/573-2277
Computing and Info. Tech.
Received on Mon Jul 21 1997 - 15:27:20 NZST