rpc.statd doesn't respect -o argument?
Chris St. Pierre
stpierre at NebrWesleyan.edu
Thu Jun 1 14:58:11 UTC 2006
I'm trying to implement iptables on a machine that, among other
things, serves as an NFS server. I've locked down all of the ports of
the various daemons, but rpc.statd doesn't appear to respect the -o
argument. As you can see:
$ ps -ef | grep statd
rpcuser 17077 1 0 09:47 ? 00:00:00 rpc.statd -p 4000 -o 4004
But:
# netstat -unlp | grep rpc.statd
udp 0 0 0.0.0.0:4000 0.0.0.0:*
17077/rpc.statd
udp 0 0 0.0.0.0:717 0.0.0.0:*
17077/rpc.statd
The second port appears to be set randomly by portmap, rather than by
the -o 4004 argument I gave it. Nothing else is using port 4004.
My /etc/sysconfig/nfs:
STATD_PORT=4000
STATD_OUTGOING_PORT=4004
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
RQUOTAD_PORT=4003
Thoughts? Thanks!
Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University
More information about the redhat-list
mailing list