From: Scott Wiersdorf <scott@bluehost.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Balbir Singh <balbir@in.ibm.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
matt@bluehost.com
Subject: Re: [PATCH 2.6.25-4] getdelays.c: signal handling for log rotation
Date: Mon, 09 Jun 2008 08:20:29 -0600 [thread overview]
Message-ID: <1213021229.4645.67.camel@tub.office.bluehost.com> (raw)
In-Reply-To: <4849E09D.6090804@firstfloor.org>
On Sat, 2008-06-07 at 03:13 +0200, Andi Kleen wrote:
> Scott Wiersdorf wrote:
> > I still think a single handler is elegant enough though, and works
> > better with many log rotation systems that want to send a single
> > signal to a pid (it's what we need where I'm working now, hence the
> > patch).
>
> Well in general it would be cool if there was nicer free userland for
> the obscure but useful delay accounting. The code in Documentation
> is really not much more than a example. Do you have something downloadable?
I don't. I'm really not much of a C programmer; I'm just hacking on this
file for our company because we have a use for it. I'm all for it going
into userland, but don't have the time to be responsible for that.
Scott
next prev parent reply other threads:[~2008-06-09 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 19:43 Scott Wiersdorf
2008-06-06 3:46 ` Balbir Singh
2008-06-06 20:40 ` Scott Wiersdorf
2008-06-06 13:59 ` Andi Kleen
2008-06-06 20:42 ` Scott Wiersdorf
2008-06-07 1:10 ` Andi Kleen
2008-06-06 20:47 ` Scott Wiersdorf
2008-06-07 1:13 ` Andi Kleen
2008-06-09 14:20 ` Scott Wiersdorf [this message]
2008-06-09 14:42 ` Balbir Singh
2008-06-30 19:52 ` Andrew Morton
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=1213021229.4645.67.camel@tub.office.bluehost.com \
--to=scott@bluehost.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@bluehost.com \
/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
all inboxes | Powered by JetHome®