From: Junio C Hamano <gitster@pobox.com>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-daemon: Simplify child management and associated logging by
Date: Tue, 12 Aug 2008 15:05:08 -0700 [thread overview]
Message-ID: <7vzlnhq48b.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080812212534.6871.19377.stgit@aristoteles.cuci.nl> (Stephen R. van den Berg's message of "Tue, 12 Aug 2008 23:25:35 +0200")
"Stephen R. van den Berg" <srb@cuci.nl> writes:
> making the signal handler almost a no-op.
> Fix the killing code to actually be smart instead of the
> pseudo-random mess.
> Get rid of the silly fixed array of children and make
> max-connections dynamic and configurable in the process.
> Make git-daemon a proper syslogging citizen with PID-info.
> Simplify the overzealous double buffering in the logroutine,
> remove the artificial maximum logline length in the process.
>
> Signed-off-by: Stephen R. van den Berg <srb@cuci.nl>
Sorry, but this does too many things in one patch.
- Taking advantage of poll() getting interrupted by SIGCHLD, so that you
do not have to do anything in the signal handler, is so obvious that I
am actually ashamed of not having to think of it the last time we
touched this code. Is there a poll() that does not return EINTR but
just call the handler and restart after that as if nothing has
happened, I have to wonder...
- Conversion from silly fixed array to dynamic and configurable maximum
would be a good idea, but that is independent from the above, isn't it?
- I see you have a call to vsyslog, which is the first user of the
function. How portable is it (the patch coming from you, I know
Solaris would have it, and recent 4BSD also would, but what about the
others)?
next prev parent reply other threads:[~2008-08-12 22:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 19:36 [PATCH] git-daemon: SysV needs the signal handler reinstated Stephen R. van den Berg
2008-08-12 21:25 ` [PATCH] git-daemon: Simplify child management and associated logging by Stephen R. van den Berg
2008-08-12 22:05 ` Junio C Hamano [this message]
2008-08-12 22:56 ` Stephen R. van den Berg
2008-08-12 23:52 ` Stephen R. van den Berg
2008-08-13 0:03 ` Stephen R. van den Berg
2008-08-13 0:07 ` Marcus Griep
2008-08-13 0:20 ` Junio C Hamano
2008-08-13 7:36 ` Stephen R. van den Berg
2008-08-13 8:23 ` Stephen R. van den Berg
2008-08-13 19:28 ` Junio C Hamano
2008-08-12 22:32 ` Alex Riesen
2008-08-12 23:12 ` Stephen R. van den Berg
2008-08-13 6:20 ` Alex Riesen
2008-08-13 7:21 ` Stephen R. van den Berg
2008-08-13 6:41 ` Andreas Ericsson
2008-08-13 7:18 ` Alex Riesen
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=7vzlnhq48b.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=srb@cuci.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.