KDC worker processes project

[John Hascall]

"Roland C. Dowdeswell" <elric at imrryr.org> writes:
> On Thu, Sep 16, 2010 at 03:44:39PM -0400, ghudson at MIT.EDU wrote:
> > I'm beginning a formal review of the KDC worker processes project,
> > ending next Friday.  The project proposal is at:
> > 
> > http://k5wiki.kerberos.org/wiki/Projects/Parallel_KDC
> 
> Another feature that would be quite small but nonetheless would
> increase robustness to some degree would be to have each child exit
> after a set period of time and/or requests.  This would reduce the
> risks of memory leaks or gradual memory corruption in the various
> DB backends.  The supervisor could restart kids as it reaps them.
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I would prefer to see this behavior instead of the proposed behavior:

  "When any child process exits, the parent will terminate the
   other worker processes and exit.

as it seems more robust.  It also might provide a reasonable path
to eliminate the rebind limitation:

  "On platforms with no IP_PKTINFO support ... disable reconfiguration
   when worker processes are in use."

John
-------------------------------------------------------------------------------
John Hascall, john at iastate.edu
Team Lead, NIADS (Network Infrastructure, Authentication & Directory Services)
IT Services, The Iowa State University of Science and Technology