From: Steve Dickson <steved@4Dicksons.org>
To: Erik Enge <eenge@prium.net>, nfs@lists.sourceforge.net
Subject: Re: How does lockd work when specifying mountd port.
Date: Tue, 21 Jan 2003 17:23:43 -0500 [thread overview]
Message-ID: <3E2DC86F.2070508@4Dicksons.org> (raw)
In-Reply-To: <87k7gyzi6i.fsf@prium.net>
it turns out with RH8.0 (maybe earlier versions as well) you can
specify the port at insmod time by setting nlm_udpport or
nlm_tcpport
You can also sett nlm_grace_period and nlm_timeout as well...
Erik Enge wrote:
>Steve Dickson <SteveD@4Dicksons.org> writes:
>
>
>
>>Lockd gets an enumerated port number and then registers
>>it with the portmapper. Then processes ask portmapper
>>(or rpcbind if your talking to Solaris) for the port. so you will
>>have to open up the port after lockd has started. IMHO, This may not
>>be too wise to opening up all these ports,
>>you might want to think of using a VPN or SSH....
>>
>>
>
>Thanks for your reply.
>
>Is there no way I can specify this port and have all processes use the
>same port and then open only that one through the firewall?
>
>I guess this means that I'm not using lockd at the moment. Not
>devastating considering we have virtually only one NFS client.
>
>Erik.
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-01-21 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 19:38 How does lockd work when specifying mountd port Erik Enge
[not found] ` <3E2CB6DF.8050409@4Dicksons.org>
[not found] ` <87k7gyzi6i.fsf@prium.net>
2003-01-21 22:23 ` Steve Dickson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E2DC86F.2070508@4Dicksons.org \
--to=steved@4dicksons.org \
--cc=eenge@prium.net \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox