Mike, AFAIK, xinetd does not determine on what port it should listen for a given service by that service's file in /etc/xinetd.d. I believe xinetd gets information about a service from the file in /etc/xinetd.d and then determines what port by the appropriate entry in /etc/services.
My /etc/services does not have anything referrencing a udp port 624, maybe yours does? Another thing you can check is to add "-d" to the "EXTRAOPTIONS" line in /etc/sysconfig/xinetd and then restart xinetd. It should dump some information about services and the ports on which they are configured to listen. -Steve -----Original Message----- From: Mike Vanecek [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 9:31 AM To: [EMAIL PROTECTED] Subject: Re: udp port 624 listening? On Thu, 7 Aug 2003 09:47:18 -0400, Hal Burgiss wrote > On Thu, Aug 07, 2003 at 08:43:57AM -0500, Mike Vanecek wrote: > > Why is xinetd listening on udp port 624? > > > > I would suggest checking rpcinfo. Thank you for the response. The more I look, the more confused I become. netstat shows udp 0 0 0.0.0.0:624 0.0.0.0:* 2144/xinetd That process does indeed belong to xinetd root 2144 0.0 0.0 2068 72 ? S Aug03 0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid Portmap is stopped [EMAIL PROTECTED] root]# service portmap status portmap is stopped [EMAIL PROTECTED] root]# rpcinfo -p rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused I have looked in /etc/rc.d/init.d to see who is starting the xinetd process, and do not have a clue. Portmap is not part of the inetd wrappered processes: [EMAIL PROTECTED] root]# d /etc/xinetd.d total 100K drwxr-xr-x 2 root root 4.0K Jun 3 22:17 ./ drwxr-xr-x 66 root root 8.0K Aug 7 08:14 ../ -rw-r--r-- 1 root root 563 Apr 16 11:13 chargen -rw-r--r-- 1 root root 580 Apr 16 11:13 chargen-udp -rw-r--r-- 1 root root 419 Apr 16 11:13 daytime -rw-r--r-- 1 root root 438 Apr 16 11:13 daytime-udp -rw-r--r-- 1 root root 341 Apr 16 11:13 echo -rw-r--r-- 1 root root 360 Apr 16 11:13 echo-udp -rw-r--r-- 1 root root 318 Jan 24 2003 finger -rw-r--r-- 1 root root 370 Jan 25 2003 imap -rw-r--r-- 1 root root 365 Jan 25 2003 imaps -rw-r--r-- 1 root root 453 Jan 25 2003 ipop2 -rw-r--r-- 1 root root 356 Apr 21 15:41 ipop3 -rw-r--r-- 1 root root 421 Apr 21 14:57 leafnode -rw-r--r-- 1 root root 275 Feb 4 2003 ntalk -rw-r--r-- 1 root root 335 Jan 25 2003 pop3s -rw-r--r-- 1 root root 312 Apr 16 11:13 servers -rw-r--r-- 1 root root 314 Apr 16 11:13 services -rw-r--r-- 1 root root 392 Jan 31 2003 sgi_fam -rw-r--r-- 1 root root 363 Apr 5 22:46 swat -rw-r--r-- 1 root root 263 Feb 4 2003 talk -rw-r--r-- 1 root root 305 Jan 29 2003 telnet -rw-r--r-- 1 root root 497 Apr 16 11:13 time -rw-r--r-- 1 root root 518 Apr 16 11:13 time-udp Something somewhere starts this process. But what and where? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
