From: Eli Carter <eli.carter@inet.com>
To: n0ano@indstorage.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] core file naming option
Date: Fri, 28 Sep 2001 14:54:34 -0500 [thread overview]
Message-ID: <3BB4D57A.C8E06654@inet.com> (raw)
In-Reply-To: <E15mHSd-0000mh-00@the-village.bc.nu> <3BB20F26.5575897B@inet.com> <20010928123453.A892@tlaloc.indstorage.com>
n0ano@indstorage.com wrote:
> Having the 2.2.x series create `core.pid' is like a 2 line change
> to `fs/binfmt_elf.c', just increase the size of the array that holds
> the file name and `sprintf' the pid into it. I've got a patch for
> the 2.2.x series that dumps core for all threads and puts them in
> `core.pid' files.
Well, when I asked Alan about it, he said "Doing it in 2.2 is incredibly
hard for internal locking reasons"... I'm not ready to tackle that.
If you have a patch that does it correctly, submit it to Alan.
I'd still like to have the option I submitted as part of 2.2 *shrug*...
it's just bringing back functionality that was in earlier versions of
Linux as a compile option. (From what I understand, this is similar to
something done in the BSDs at some time in the past... but being a young
whippersnapper, I don't really know.)
Eli
--------------------. Real Users find the one combination of bizarre
Eli Carter \ input values that shuts down the system for days.
eli.carter(a)inet.com `-------------------------------------------------
next prev parent reply other threads:[~2001-09-28 19:54 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
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 [this message]
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=3BB4D57A.C8E06654@inet.com \
--to=eli.carter@inet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n0ano@indstorage.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