SCIENTIFIC-LINUX-USERS Archives

August 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Edison, Arul (GE Healthcare)" <[log in to unmask]>
Reply To:
Edison, Arul (GE Healthcare)
Date:
Tue, 20 Aug 2013 05:49:43 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Hi Konstantin Olchanski,

Can you provide some more info on how to disable / configure portmap?
Below is the rpcbind rpm that is in the system
 rpcbind-0.2.0-9.el6.x86_64

Thanks,
Arul

 

-----Original Message-----
From: Konstantin Olchanski [mailto:[log in to unmask]] 
Sent: Friday, August 16, 2013 11:55 PM
To: Edison, Arul (GE Healthcare)
Cc: Scientific Linux; S, Akshata (GE Healthcare); Rao, Keshava N (GE Healthcare)
Subject: Re: UDP message not recevied at port 8100 with Scientific Linux 6.3

On Fri, Aug 16, 2013 at 02:01:20PM +0000, Edison, Arul (GE Healthcare) wrote:
> Hi all,
>                 The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server
> Is there a way to disable the xprint-server    ?
>


You can use "lsof" to find out who is consuming UDP packets sent to port 8100.

Note that UDP port collisions is a problem because "portmap" ("rpcbind") assigns UDP ports to various daemons kind of randomly and it will eventually collide with any UDP port you decide to chose. One way to avoid this is by using portmap yourself in your application.

(Also check that your packets are not rejected by your own firewall, "iptables -L -v").


--
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2