On Tue, Jan 11, 2005 at 10:41:00PM -0500, Chip Salzenberg wrote:
> According to Mark Ferlatte:
> > I think that rpc.statd should be assigned a port that doesn't conflict
> > with anything else and that it should just use that, at least on Debian.
>
> Hm. That would break precedent with other Sun RPC programs, I think.
> I won't close the bug though, I'd like to see other commentary.
The rpc.statd daemon can supposedly be configured to use a specific port
by supplying the -p argument to rpc.statd. The Debian way is to edit
/etc/default/nfs-common, supplying the STATDOPTS shell variable with the
argument, for instance:
STATDOPTS='-p 4000'
The '-p' option is described in the rpc.statd man page...
HOWEVER, this is somewhat broken, in that rpc.statd seems to open
*three* listeners; one TCP and *two* UDP. The TCP and one UDP listener
heed the -p configuration, but the second UDP listener is still rogue.
So, leaving aside my opinion of daemons that randomly bind privileged
(or not) ports, I think we may have a real bug.
nfs-common 1.0.6-3.1
nfs-user-server 2.2beta47-20
-ph
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
