From owner-freebsd-questions  Tue Nov 21 01:49:39 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA02173
          for questions-outgoing; Tue, 21 Nov 1995 01:49:39 -0800
Received: from bsd.rrze.uni-erlangen.de (root@bsd.rrze.uni-erlangen.de [131.188.77.76])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA01780
          for <questions@freebsd.org>; Tue, 21 Nov 1995 01:47:33 -0800
Received: from billa.rrze.uni-erlangen.de by bsd.rrze.uni-erlangen.de with ESMTP;
	id KAA00618 (8.6.11/7.3s-FAU); Tue, 21 Nov 1995 10:47:09 +0100
From: Falko Dressler <fd@bsd.rrze.uni-erlangen.de>
Message-Id: <199511210947.KAA00618@bsd.rrze.uni-erlangen.de>
Subject: svcupd_create(RPC_ANYSOCK)
To: questions@freebsd.org
Date: Tue, 21 Nov 1995 10:47:07 +0100 (MET)
X-Mailer: ELM [version 2.4 PL24 ME7a]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Length: 771       
Sender: owner-questions@freebsd.org
Precedence: bulk

Hello,

I noticed that you get only reserved ports if you make a
svcudp_create(RPC_ANYSOCK) which results in a bindresvport()
in svc_udp.c (libc).
I think that this could be a real bug because these portnumbers
are used by real daemons like kerberos which uses port 750 as well.
Actually I've run in large problems caused by this strategie of
selecting ports for rpc services (mountd, ypbind, ypserv etc.)
because some servers start and shut down shortly with the
reason Can't bind to socket.
I have had a look to other operating systems like Solaris
and found out the the used ports for the rpc services start
at about 32000.
Do you have a real reason for your strategie for giving rpc ports?

Falko.

-- 
Falko Dressler              Falko.Dressler@rrze.uni-erlangen.de