Package: nfs-common
Version: 1:1.0.6-3.1
Severity: important

www1:~# cat /etc/default/nfs-common 
# Options for rpc.statd.
#   Should rpc.statd listen on a specific port?
#   If so, set this variable to a statd argument like: "--port 1000".
STATDOPTS="--port 900 -o 901"

# Are you _sure_ that your kernel does or does not need a lockd daemon?
# If so, set this variable to either "yes" or "no".
NEED_LOCKD=
www1:~# netstat -taupn|grep statd
tcp        0      0 0.0.0.0:900             0.0.0.0:*               LISTEN      
1360/rpc.statd      
udp        0      0 0.0.0.0:900             0.0.0.0:*           1360/rpc.statd  
    
udp        0      0 0.0.0.0:688             0.0.0.0:*           1360/rpc.statd  
    

Documentation says:
man rpc.statd
       -o, --outgoing-port port
              specify a port for rpc.statd to  send  outgoing  status requests  
from.   By  default,  rpc.statd  will  ask
              portmap(8)  to assign it a port number.  As of this writing, 
there is not a standard port number that portmap
              always or usually assigns.  Specifying a port may be useful when 
implementing a firewall.

Neither -o or --outgoing-port seems to be working.

It is very important to be able to control the open/bound ports.

In my case rpc.statd stole the port from heartbeat.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.14
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages nfs-common depends on:
ii  debconf                     1.4.30.13    Debian configuration management sy
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libwrap0                    7.6.dbs-8    Wietse Venema's TCP wrappers libra
ii  portmap                     5-9          The RPC portmapper
ii  sysvinit                    2.86.ds1-1   System-V like init

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to