...[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.
I must be doing something wrong, since it had not given me the same informatinon you show above. The only way I could find it, based on the suggestion of another poster, was to stop sig_fam and note that the connection was closed.
Restart xinetd after you start portmap and you'll get better results.
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.
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
