This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH]:bindresvport should check /etc/services


                                                                                                           
                      Ulrich Drepper                                                                       
                      <drepper@redhat.c        To:       Rajasekhar Inguva/India/IBM@IBMIN                 
                      om>                      cc:       libc-alpha@sources.redhat.com                     
                                               Subject:  Re: [PATCH]:bindresvport should check             
                      11/26/2002 11:27          /etc/services                                              
                      AM                                                                                   
                                                                                                           
                                                                                                           







-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rajasekhar Inguva wrote:

> The glibc routine bindresvport(), in it's current implementation,
randomly
> tries to a bind to a port number in the range 600-1023.

>>And this is the right implementation.  If it's causing problems your
>> setup is wrong.

I didnt quite get the justification of grabbing a port which is 'well
known' by way of establishing itself in /etc/services.
      If rule 1 is "All well known services wanting to bind to ports in
range 0-1023 should do so as per listings in /etc/services"
      then rule 2 should be "If i need a random reserved port, I better
skip the ports which are legally assigned to well known services"

Am i missing something or am i confused ? Please clear me up on this.

Thank you !,

Best Regards,
Raj Inguva





Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]