The inetd-process complaining have PID 190.
Looka at the process and see what process the parent
is (PPID).
If it occurs on a regular basis it could be like
kidambi said, something is trying to start a new inetd
but it could also be that inetd dies for some reason and
restarts.
Check /var/adm/messages if you have any termination message
from inetd. otherwise strat it in a terminalwindow and
you will see if anything happens.
HTH
Main Topics
Browse All Topics





by: k.kidambiPosted on 2002-12-04 at 08:40:34ID: 7531897
hi, rsalunkhe
Looks like some process is starting your inetd daemon. Look at your cron jobs or at jobs. which may be causing this problem.
if you don't find any jobs, try to stop inetd and restart that should clear the problem. If this is a critical production server try to stop and start inetd in a maintenance window, so that you don't impact any users / system processes.
try your luck.
kidambi