On Thu, 7 Aug 2003 11:22:32 -0400, Hal Burgiss wrote
On Thu, Aug 07, 2003 at 10:19:57AM -0500, Mike Vanecek wrote:
I just want to know why xinetd has a udp port open. As I am now
discovering, that port number changes whenever xinetd is restarted.
Which is a defining characteristic of
Mike Vanecek wrote:
[EMAIL PROTECTED] root]# service portmap start
Starting portmapper: [ OK ]
[EMAIL PROTECTED] root]# rpcinfo -p
program vers proto port
102 tcp111 portmapper
102 udp111 portmapper
[EMAIL
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.
--
Hal Burgiss
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
On Thu, Aug 07, 2003 at 10:19:57AM -0500, Mike Vanecek wrote:
I just want to know why xinetd has a udp port open. As I am now
discovering, that port number changes whenever xinetd is restarted.
Which is a defining characteristic of RPC services ...
The suggestion to look at rpcinfo, rpc,
-Original Message-
From: Hal Burgiss [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: udp port 624 listening?
Care to wager? I am betting on sgi_fam.
A quick google search brought up some similar threads, fam came up
On Thu, 07 Aug 2003 18:48:34 -0700, Gordon Messmer wrote
Mike Vanecek wrote:
[EMAIL PROTECTED] root]# service portmap start
Starting portmapper: [ OK ]
[EMAIL PROTECTED] root]# rpcinfo -p
program vers proto port
102 tcp
On Thu, 7 Aug 2003 10:27:19 -0500, Rigler, Steve wrote
-Original Message-
From: Hal Burgiss [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: udp port 624 listening?
Care to wager? I am betting on sgi_fam.
A quick
.
-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
-Original Message-
From: Mike Vanecek [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 9:59 AM
To: [EMAIL PROTECTED]
Subject: RE: udp port 624 listening?
This is a RH 9 system, does that make a difference?
I don't really see why there would be a difference, but I am
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
On Thu, 07 Aug 2003 15:07:42 -0700, Gordon Messmer wrote
Mike Vanecek wrote:
[EMAIL PROTECTED] root]# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection
...
The suggestion to look at rpcinfo, rpc, and portmapper really has no relevance
to the issue.
Yes,
On Thu, 07 Aug 2003 08:13:41 -0700, Gordon Messmer wrote
Mike Vanecek wrote:
Portmap is stopped
...
[EMAIL PROTECTED] root]# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection
refused
I do not want portmapper running.
I just want to know why xinetd has a
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
Mike Vanecek wrote:
Portmap is stopped
...
[EMAIL PROTECTED] root]# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
So start the portmapper, and try again.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
On Thu, 2003-08-07 at 06:43, Mike Vanecek wrote:
Why is xinetd listening on udp port 624?
udp0 0 0.0.0.0:624 0.0.0.0:*
2144/xinetd
I have looked at grep 624 /etc/xinetd.d and found nothing. Where else should
I look?
OK, rather than
Mike Vanecek wrote:
[EMAIL PROTECTED] root]# rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection
...
The suggestion to look at rpcinfo, rpc, and portmapper really has no relevance
to the issue.
Yes, it does. The variable port is a signature of portmap
16 matches
Mail list logo