[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070329141715.71a6abae.akpm@linux-foundation.org>
Date: Thu, 29 Mar 2007 14:17:15 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Howells <dhowells@...hat.com>
Cc: Pavel Machek <pavel@....cz>,
"Kawai, Hidehiro" <hidehiro.kawai.ez@...achi.com>,
kernel list <linux-kernel@...r.kernel.org>,
Robin Holt <holt@....com>, Alan Cox <alan@...rguk.ukuu.org.uk>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
sugita <yumiko.sugita.yf@...achi.com>,
Satoshi OSHIMA <soshima@...hat.com>,
Hideo AOKI <haoki@...hat.com>
Subject: Re: [PATCH 1/4] coredump: add an interface to control the core dump
routine
On Thu, 29 Mar 2007 20:16:59 +0100
David Howells <dhowells@...hat.com> wrote:
> Pavel Machek <pavel@....cz> wrote:
>
> > > Userland core dumper is useful because it is relatively easy to be
> > > customized, but its reliability highly depends on the application
> > > programs.
> >
> > Fix userland core dumper to be reliable, then.
>
> I don't think it's that easy. The userland core dumper, as I understand it,
> has to work *within* an application program (it's a library), thus the
> application program my scotch the core dumper in a couple of ways:
That's no longer necessarily true with the recently-added
dump-to-an-application feature:
core_pattern:
...
. If the first character of the pattern is a '|', the kernel will treat
the rest of the pattern as a command to run. The core dump will be
written to the standard input of that program instead of to a file.
That's new in 2.6.20 (maybe .19?) so people probably don't know about it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists