[Bug libc/1936] Improvement to rcmd

["drepper at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From drepper at redhat dot com  2006-04-23 18:26 -------
The argument about robustness is bogus.  We will always iterate over all
possible ports if necessary.  The only thing which could be said is that we try
to many times the ports which might be crowded by other rcmd calls and this way
cause delays.

But a limited amount of randomization will only help a bit.  The next person
will come and complain that the randomization is too small.  But sooner or later
we'll run into problems with ports which are explicitly requested by
applications and who then couldn't run.  Any change in the way ports are tried
will increase the chance that this can happen.

Combine this with the fact that nobody really should use rcmd() etc the best
solution is to not change anything.  Maybe this will entice people to refrain
from using rcmd() which is the best outcome one can hope for.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/bugzilla/show_bug.cgi?id=1936

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.