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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
