From: Padraig Brady <padraig@antefacto.com>
To: Eli Carter <eli.carter@inet.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] core file naming option
Date: Wed, 26 Sep 2001 12:30:25 +0100 [thread overview]
Message-ID: <3BB1BC51.4070102@antefacto.com> (raw)
In-Reply-To: <3BB104A9.3AD512A5@inet.com>
Eli Carter wrote:
>Alan et. all,
>
>The attached patch adds an option to the build to have core files named
>core.processname, but defaulting to the current behaviour of course.
>For most people the single 'core' file is sufficient, but when the sky
>is falling, it's nice to have more places for it to land. :)
>So, is this something that might go into the kernel, or are their
>philisophical reasons against it? (The patch is against 2.2.19. I
>haven't looked at 2.4.x yet. Let me know if you want a 2.4 or if I
>should send it to Linus, or...)
>
>Questions, comments, etc. welcome,
>
Other Unix' have used core.pid as the name. Wouldn't this be better?
Especially when the process name is already stored in a core file
(`file core` will give you this). Hmm I wonder could we use this
core.pid format to dump the core for each thread (probably a bad idea).
Padraig.
next prev parent reply other threads:[~2001-09-26 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 22:26 [PATCH] core file naming option Eli Carter
2001-09-26 11:30 ` Padraig Brady [this message]
2001-09-26 16:22 ` Alan Cox
2001-09-26 17:23 ` Eli Carter
2001-09-28 18:34 ` n0ano
2001-09-28 19:54 ` Eli Carter
2001-09-27 16:17 ` bill davidsen
2001-09-27 17:09 ` Eli Carter
-- strict thread matches above, loose matches on Subject: below --
2001-10-08 21:32 Phil Edwards
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=3BB1BC51.4070102@antefacto.com \
--to=padraig@antefacto.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eli.carter@inet.com \
--cc=linux-kernel@vger.kernel.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 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.