Not same error in log. (and I'm concerned that *something* in xinetd may
have been important) typing "ps -ef | grep xinetd" gives me. root 5248 1 0 Feb22 ? 00:00:01 xinetd -stayalive -
pidfile /var/run/xinetd.pid
is it safe to kill that ps?
try first to kill -TERM and then with -9 (KILL KILL!). Remember also disable xinetd startup using "chkconfig xinetd off"
-- Eero