On Thu, 7 Aug 2003 09:38:28 -0500, Rigler, Steve wrote
> 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?

Mine either.

> 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.

Did that and did not see anything. I guess that mode puts one into interactive
mode. I had to ^C to get out of it on the console which prevented xinetd from
loading. I removed the option, and did another service xinetd restart and now
the port number has changed!!??

[EMAIL PROTECTED] root]# netstat -natpu | grep xinetd
tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN   
  20512/xinetd
tcp        0      0 0.0.0.0:119             0.0.0.0:*               LISTEN   
  20512/xinetd
udp        0      0 0.0.0.0:760             0.0.0.0:*                        
  20512/xinetd
[EMAIL PROTECTED] root]# ps aux | grep xinetd
root     20512  0.0  0.2  2068  920 ?        S    09:50   0:00 xinetd
-stayalive -pidfile /var/run/xinetd.pid

Although a 760/tcp is defined, a 760/udp is not defined in /etc/serices.

This is a RH 9 system, does that make a difference?

Could this be some form of xinetd port used to communicate amoung itself (sort
of a xinetd loopback)?

If you do a netstat -natpu | grep xinetd you are not seeing the same thing?



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to