Skip to contentSkip to conversation

statd not binding to outgoing-port

DISCUSSION Andrew Glen-Young 1 participant 1 message Oct 24, 2002

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello All,

I've been through the NFS-HOWTO and have decided to bind the rpc daemons to specified ports. I have been successful with all but one daemon: rpc.statd. When I run rpc.statd -p 32765 -o 32766, the daemon correctly binds to port 32765 but not to 32766. Rather it binds to a low numbered port - 761, 833, etc. Nothing else is bound to the port: 32766. Rpc.statd seems to be ignoring the -o flag?

I am using Linux 2.4.19 vanilla kernel, portmap v5 and have tried the vanilla sources for nfs-utils-0.3.3 and nfs-utils-1.0.1, both with the same result.

I was wondering whether this is a bug or mere stupidity...

Thanks for your time,

Signature · 14 lines
=========================================================
Andrew Glen-Young           Phone:        +27 21 426-5252  
iafrica.com                 Fax:          +27 21 426-5453
Systems Administrator       Mail:   [email protected]


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en
_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs