This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: [han.holl@pobox.com] libc/1172: rresvport should avoid wellknown ports
- To: Han Holl <han.holl@pobox.com>
- Subject: Re: [han.holl@pobox.com] libc/1172: rresvport should avoid wellknown ports
- From: "Rod m. Stewart" <stewart@nexus.carleton.ca>
- Date: Tue, 29 Jun 1999 22:40:41 -0400 (EDT)
- cc: Thorsten Kukuk <kukuk@suse.de>, libc-alpha Mailinglist <libc-alpha@sourceware.cygnus.com>
On Mon, 28 Jun 1999, Han Holl wrote:
> On Mon, Jun 28, 1999 at 09:34:39AM +0200, Thorsten Kukuk wrote:
> >
> > You make one mistake: You looked at the RedHats /etc/services version.
> > This means, on RedHat 17 ports out of 424 are used. But RedHats
> > version is not an official one.
> >
> Of course each system administrator _knows_ which services he runs.
> Systems running obscure services wil have administrators who know
> how to edit /etc/services, so as to let enough port free for
> dynamically assigned ports. I didn't propose to avoid all reserved ports,
> but all reserved ports that are actually configured in /etc/services.
>
> > Look at RFC 1700, nearly all ports are reserved for a service.
Just one comment. Please disregard it if it is not feasible. Would it be
possible to first try to get a reserved port which is not in set in
/etc/services, then if it fails (none available) fall back on the current
behaviour.
Or is would this add in too much over head, or I may have misunderstood
the question/problem.
-Rms