On Mon, 15 Jun 2009, Shawn O. Pearce wrote:
But I have to wonder, why are we doing this? Why can't we teach the
individual server program to record its error to the syslog before
it aborts? Are we looking for SIGSEGV or something? Its only the
daemon program staying around in memory, but that's a lot of little
daemons doing nothing waiting for their children to terminate.
Those daemons certainly have very little in terms of private data memory
usage, so all of them will share the same memory pages in practice. And
it is certainly best to have only one location to deal with syslog usage
than having each server programs to do it, after figuring out if they
are actually invoked in a context that requires syslog instead of
stderr. Having the git daemon deal with syslog, and log any abnormal
exit code from the programs it spawn is IMHO a pretty logical thing to
do.
Nicolas