Jeff Trawick wrote:
After a fix to prevent the fork bomb during slow child startup is
applied, something REALLY strange and completely unanticipated has to
happen to get the "scoreboard is full, not at MaxClients" message.
True?
true. no clue what else might trigger it at this point.
Otherwise, seeing one of these messages shouldn't prevent us
from ever seeing the other.
ok, peace. my thought was that either condition needs to be fixed ASAP.
From a user support perspective, it is very handy to be able to have
the user grep for "server reached MaxClients" to rule out a particular
type of issue, without worrying if some odd temporary situation hid
that message forever.
I worry more about the opposite - not seeing the new message due to a prior MaxClients.
but point taken, revised patch committed.
Greg
