From: "H. Peter Anvin" <hpa@zytor.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Johannes Sixt <j6t@kdbg.org>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] daemon: send stderr of service programs to the syslog
Date: Mon, 15 Jun 2009 12:06:01 -0700 [thread overview]
Message-ID: <4A369B99.4030504@zytor.com> (raw)
In-Reply-To: <20090615145716.GW16497@spearce.org>
Shawn O. Pearce wrote:
>
> They could, if they were broken. :-)
>
> IIRC only upload-pack produces progress (from pack-objects).
> It does so by using a pipe on fd 2, and either copying it down
> to the client via side-band, or discarding it. So progress data
> shouldn't ever appear on upload-pack's own fd 2, which means you
> won't get it in this syslog thing.
>
> 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.
> Seems like a waste to me.
>
Actually, even logging signals would be useful, so I think this makes
sense. The daemon process is pretty trivial compared to the rest of the
stuff being spawned.
-hpa
next prev parent reply other threads:[~2009-06-15 19:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 20:38 [PATCH] daemon: send stderr of service programs to the syslog Johannes Sixt
2009-06-15 14:57 ` Shawn O. Pearce
2009-06-15 15:34 ` Nicolas Pitre
2009-06-15 19:06 ` H. Peter Anvin [this message]
2009-06-15 21:24 ` [PATCH] upload-pack: squelch progress indicator if client does not request sideband Johannes Sixt
2009-06-15 21:53 ` Junio C Hamano
2009-06-16 1:16 ` Nicolas Pitre
2009-06-16 5:02 ` Junio C Hamano
2009-06-16 18:03 ` Nicolas Pitre
2009-06-16 18:41 ` Johannes Sixt
2009-06-16 18:57 ` Junio C Hamano
2009-06-16 19:46 ` Nicolas Pitre
2009-06-15 21:39 ` [PATCH] daemon: send stderr of service programs to the syslog Johannes Sixt
2009-06-15 21:43 ` H. Peter Anvin
2009-06-16 20:27 ` Johannes Sixt
2009-06-16 20:30 ` H. Peter Anvin
2009-06-19 20:26 ` Junio C Hamano
2009-06-20 19:25 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A369B99.4030504@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).