git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] daemon: send stderr of service programs to the syslog

From
Nicolas Pitre <nico@cam.org>
Date
Jun 15, 2009, 15:34 UTC
Message-ID
<alpine.LFD.2.00.0906151117560.16467@xanadu.home>
In-Reply-To
<20090615145716.GW16497@spearce.org>
On Mon, 15 Jun 2009, Shawn O. Pearce wrote:
Show 5 quoted lines
> 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
Previous: Shawn O. PearceNext: H. Peter Anvin
Message 3 of 18 in “daemon: send stderr of service programs to the syslog”
  1. daemon: send stderr of service programs to the syslogJohannes Sixt, Jun 14, 2009
  2. Shawn O. PearceJun 15, 2009
  3. Nicolas PitreJun 15, 2009
  4. H. Peter AnvinJun 15, 2009
  5. upload-pack: squelch progress indicator if client does not request sidebandJohannes Sixt, Jun 15, 2009
  6. Junio C HamanoJun 15, 2009
  7. Nicolas PitreJun 16, 2009
  8. Junio C HamanoJun 16, 2009
  9. Nicolas PitreJun 16, 2009
  10. Johannes SixtJun 16, 2009
  11. Junio C HamanoJun 16, 2009
  12. Nicolas PitreJun 16, 2009
  13. Johannes SixtJun 15, 2009
  14. H. Peter AnvinJun 15, 2009
  15. Johannes SixtJun 16, 2009
  16. H. Peter AnvinJun 16, 2009
  17. Junio C HamanoJun 19, 2009
  18. Johannes SixtJun 20, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.