Gerhard Sittig <Gerhard.Sittig@gmx.net> wrote:

On Sat, Sep 02, 2000 at 12:21 +0200, Matthias Krawen wrote:

...

[ ... 111 for portmapper, 2049 for nfs ... ]

Is this a "given" or is it just "observed many times and usually done so"?

This is "given". The portmapper must be found on it's well known port, i.e. 111, to be useful. The nfsd can be configured to use another port, but defaults to 2049.

I'm not clear about how determined or fix this knowledge is (and I thought the thread's originator watched NFS using different and mostly unpredictable ports).

There are some more daemons (e.g., mountd, statd, lockd) used by NFS, and they use dynamically allocated ports. I.e., their port numbers are not fixed and must be looked up at runtime via the portmapper. Eilert -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Eilert Brinkmann -- Universitaet Bremen -- FB 3, Informatik eilert@informatik.uni-bremen.de - eilert@tzi.org - eilert@linuxfreak.com http://www.informatik.uni-bremen.de/~eilert/