Here's what I get in my logs:
[...]
Jan 16 13:17:45 bluemeanie xinetd[10119]: Reading included configuration file: /etc/xinetd.d/amanda [line=13]
Jan 16 13:17:45 bluemeanie xinetd[10119]: Protocol udp not in /etc/protocols [line=8]
Jan 16 13:17:45 bluemeanie xinetd[10119]: Error parsing attribute protocol - DISABLING SERVICE [line=8]
Jan 16 13:17:46 bluemeanie xinetd[10119]: Protocol tcp not in /etc/protocols [line=22]
Jan 16 13:17:46 bluemeanie xinetd[10119]: Error parsing attribute protocol - DISABLING SERVICE [line=22]
Jan 16 13:17:46 bluemeanie xinetd[10119]: Protocol tcp not in /etc/protocols [line=34]
Jan 16 13:17:46 bluemeanie xinetd[10119]: Error parsing attribute protocol - DISABLING SERVICE [line=34]
Jan 16 13:17:46 bluemeanie xinetd[10119]: Reading included configuration file: /etc/xinetd.d/chargen-tcp [line=42]
Jan 16 13:17:47 bluemeanie xinetd[10119]: Protocol tcp not in /etc/protocols [line=9]
Jan 16 13:17:47 bluemeanie xinetd[10119]: Error parsing attribute protocol - DISABLING SERVICE [line=9]
Obviously I've checked /etc/protocols for tcp and udp:
[...] tcp 6 TCP # transmission control protocol udp 17 UDP # user datagram protocol
And verified that /etc/protocols is readable: -rw-r--r-- 1 root root 1.8K Jan 2 09:44 /etc/protocols
My past experience with xinetd has generally been pretty good - it usually just works baring any silly config file errors. Anyone have any ideas?
Bryn
Bryn Hughes Network Specialist Linux/OS X Support Vancouver Community College
-- [EMAIL PROTECTED] mailing list
