nlm_udpport vs. udpport vs lockd.nlm_udpport vs etc.

nlm_udpport vs. udpport vs lockd.nlm_udpport vs etc.

[BuraphaLinux Server]

I am attempting to setup a firewall for an NFS v3 server.  I need to know where
the lockd ports will be.  I have added an append line to my lilo.conf
that looks like
this, and it was working in the 2.4 kernels:

append="lockd.nlm_udpport=32768 lockd.nlm_tcpport=32768"

I am using kernel 2.6.15 from ftp.kernel.org and I am trying to learn
what to do.
But the file fs/lockd/svc.c seems to want this without the 'lock.' in front.
But the file Documentation/kernel-parameters.txt suggests
lockd.udpport and lockd.tcpport (no "nlm_").

1.  Why do the files in the kernel disagree with each other?
2.  What do I really need on my append="" line, or is there some other
     way to set this now?
3.  Should I hardcode the ports in the kernel source code and recompile?

Thank you,

JGH

Re: nlm_udpport vs. udpport vs lockd.nlm_udpport vs etc.

[Randy.Dunlap]

On Sat, 14 Jan 2006 12:30:18 +0700 BuraphaLinux Server wrote:

> I am attempting to setup a firewall for an NFS v3 server.  I need to know where
> the lockd ports will be.  I have added an append line to my lilo.conf
> that looks like
> this, and it was working in the 2.4 kernels:
> 
> append="lockd.nlm_udpport=32768 lockd.nlm_tcpport=32768"
> 
> I am using kernel 2.6.15 from ftp.kernel.org and I am trying to learn
> what to do.
> But the file fs/lockd/svc.c seems to want this without the 'lock.' in front.
> But the file Documentation/kernel-parameters.txt suggests
> lockd.udpport and lockd.tcpport (no "nlm_").
 
OK, I'll send a patch for that this weekend.  It should be:

  lockd.nlm_udpport=N  lockd.nlm_tcpport=M

when built into the kernel
image.  If built as loadable modules, it is just
  modprobe lockd nlm_udpport=N nlm_tcpport=M


> 1.  Why do the files in the kernel disagree with each other?

No idea.

> 2.  What do I really need on my append="" line, or is there some other
>      way to set this now?
> 3.  Should I hardcode the ports in the kernel source code and recompile?

If above doesn't work, it would be much better if you filed a bug on it.

---
~Randy

[PATCH] nlm kernel-parameters update

[Randy.Dunlap]

From: Randy Dunlap <rdunlap@xenotime.net>

Add 2 lockd kernel parameters and spell 2 others correctly.

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
 Documentation/kernel-parameters.txt |   12 ++++++++++--
 1 files changed, 10 insertions(+), 2 deletions(-)

--- linux-2615-g9.orig/Documentation/kernel-parameters.txt
+++ linux-2615-g9/Documentation/kernel-parameters.txt
@@ -712,9 +712,17 @@ running once the system is up.
 	load_ramdisk=	[RAM] List of ramdisks to load from floppy
 			See Documentation/ramdisk.txt.
 
-	lockd.udpport=	[NFS]
+	lockd.nlm_grace_period=P  [NFS] Assign grace period.
+			Format: <integer>
+
+	lockd.nlm_tcpport=N	[NFS] Assign TCP port.
+			Format: <integer>
 
-	lockd.tcpport=	[NFS]
+	lockd.nlm_timeout=T	[NFS] Assign timeout value.
+			Format: <integer>
+
+	lockd.nlm_udpport=M	[NFS] Assign UDP port.
+			Format: <integer>
 
 	logibm.irq=	[HW,MOUSE] Logitech Bus Mouse Driver
 			Format: <irq>


---