reinstalling SIGCHLD handler before wait()

[Kevin Steves]

HP-UX 11 is looping on SIGCHLD/sigchld_handler2() when exiting a
protocol 2 session apparently because we don't call wait before
reinstalling the handler.  Any thoughts on this issue or how to address
it?

serverloop.c from latest snapshots:

void
sigchld_handler2(int sig)
{
	int save_errno = errno;
	debug("Received SIGCHLD.");
	child_terminated = 1;
	signal(SIGCHLD, sigchld_handler2);
	errno = save_errno;
}

from signal(5) on HP-UX 11 (SIGCLD is the same as SIGCHLD):

                If one of the signal interface routines is used to
                          set the action for SIGCLD to be caught (that is, a
                          function address is supplied) in a process that
                          currently has terminated (zombie) children, a
                          SIGCLD signal is delivered to the parent process
                          immediately.  Thus, if the signal-catching
                          function reinstalls itself, the apparent effect is
                          that any SIGCLD signals received due to the death
                          of children while the function is executing are
                          queued and the signal-catching function is
                          continually reentered until the queue is empty.
                          Note that the function must reinstall itself after
                          it calls wait(), wait3(), or waitpid().  Otherwise
                          the presence of the child that caused the original
                          signal causes another signal immediately,
                          resulting in infinite recursion.