public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: n0ano@indstorage.com
To: Eli Carter <eli.carter@inet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] core file naming option
Date: Fri, 28 Sep 2001 12:34:53 -0600	[thread overview]
Message-ID: <20010928123453.A892@tlaloc.indstorage.com> (raw)
In-Reply-To: <E15mHSd-0000mh-00@the-village.bc.nu> <3BB20F26.5575897B@inet.com>
In-Reply-To: <3BB20F26.5575897B@inet.com>; from eli.carter@inet.com on Wed, Sep 26, 2001 at 12:23:50PM -0500

Eli-

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.

On Wed, Sep 26, 2001 at 12:23:50PM -0500, Eli Carter wrote:
> Alan Cox wrote:
> > 
> > > 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).
> > 
> > The -ac tree and latest -linus can use core.pid for each thread already
> 
> Ah, I see: /proc/sys/kernel/core_uses_pid if I'm not mistaken.
> 
> However, my primary interest is with the 2.2.x series, and I don't see
> this in 2.2.19.
> Is this something that will be moving to 2.2.19?  Are there
> philisophical or technical reasons one way or the other?
> 
> Thank you for your time,
> 
> 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 `-------------------------------------------------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117

  reply	other threads:[~2001-09-28 18:16 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 [this message]
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=20010928123453.A892@tlaloc.indstorage.com \
    --to=n0ano@indstorage.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox