From: Jeff Dike <jdike@addtoit.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Andi Kleen <andi@firstfloor.org>,
"Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [Feature Request?] Inline compression of process core dumps
Date: Fri, 13 Apr 2007 00:21:56 -0400 [thread overview]
Message-ID: <20070413042156.GA12786@c2.user-mode-linux.org> (raw)
In-Reply-To: <461EF1A1.3070102@theshore.net>
On Thu, Apr 12, 2007 at 10:57:37PM -0400, Christopher S. Aker wrote:
> The process is a UML instance (skas mode, so at least a kernel,
> userspace, and io thread), which will generate a single, usable, core
> file just fine with a non-pipe core_pattern...
Yeah, but can you get a core file without the .pid on the end? I just
tried, with core_pattern == core and core_uses_pid == 0, and I still
got core.pid.
I can fix this on my end - just have to kill off a bunch of things
before aborting.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2007-04-13 4:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 15:52 [Feature Request?] Inline compression of process core dumps Christopher S. Aker
2007-04-12 16:09 ` Bill Rugolsky Jr.
2007-04-12 16:18 ` Guillaume Chazarain
2007-04-12 16:28 ` Alan Cox
2007-04-12 16:42 ` Bill Rugolsky Jr.
2007-04-12 17:45 ` Andi Kleen
2007-04-13 2:22 ` Christopher S. Aker
2007-04-13 2:38 ` Randy Dunlap
2007-04-13 2:57 ` Christopher S. Aker
2007-04-13 4:21 ` Jeff Dike [this message]
2007-04-13 10:55 ` Alan Cox
2007-04-13 12:23 ` Andi Kleen
2007-04-13 14:59 ` Randy Dunlap
2007-04-13 15:43 ` Andi Kleen
2007-04-13 16:17 ` Alan Cox
2007-04-13 19:42 ` Andi Kleen
2007-04-13 12:39 ` Alan Cox
2007-04-13 13:38 ` Christopher S. Aker
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=20070413042156.GA12786@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=brugolsky@telemetry-investments.com \
--cc=caker@theshore.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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