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
> >     100000    2   tcp    111  portmapper
> >     100000    2   udp    111  portmapper
> > 
> > [EMAIL PROTECTED] root]# netstat -naup
> ...
> > udp        0      0 0.0.0.0:916             0.0.0.0:*                        
> >   21092/xinetd
> 
> Testing indicates that portmap must be running when a portmap 
> service starts in order for it to be registered properly.  Portmap 
> services won't re-register with a portmap that starts up later.  
> You'd have to restart xinted after starting portmap to get valid data.
> 
> Thats new info to me, but there you go.

Now I get the same results as you had before:

[EMAIL PROTECTED] root]# rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    391002    2   tcp  54878  sgi_fam

> > I have never found any use for portmapper, hence do not run it. Am I missing
> > something?
> 
> Yes.  Local RPC services use the portmapper.
> 
> > I run sig_fam only because I have been told it improves the operation of some
> > apps. Despite my reading about it, I never have quite understood what it
> > really does. I am tempted to shut it down and see what happens.
> 
> FAM is the File Alertation Monitor.  It uses a kernel service to 
> monitor files and directories for modifications, rather than poll(), 
> select() or stat() the files/directories repeatedly.
> 
> If your portmapper is running, and fam is registered with it, an 
> open Nautilus window should immediately reflect any changes made to 
> the files/directories it displays.
> 
> Other GNOME applications use FAM as well.  I believe that the text 
> editor will use it to watch for changes to files it has open.

I find it interesting to note that the configuration of portmap and sig_fam
totally changes. Portmap now makes a tcp and udp connection. The xinetd
connection attributed to sig_fam now moves from a udp connection to a tcp
connection.

[EMAIL PROTECTED] root]# netstat -natup
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State    
  PID/Program name
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN   
  29966/portmap

tcp        0      0 127.0.0.1:54878         0.0.0.0:*               LISTEN   
  29995/xinetd

udp        0      0 0.0.0.0:111             0.0.0.0:*                        
  29966/portmap

Can't remember, but seems like these connections created a lot of packet
activity. I guess I will watch the logs for a while.


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

Reply via email to