All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Sinz <msinz@wgate.com>
To: Andrew Morton <akpm@digeo.com>
Cc: mks@sinz.org, marcelo@conectiva.com.br,
	Robert Love <rml@tech9.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	riel@conectiva.com.br, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] kernel 2.4.19 & 2.5.38 - coredump sysctl
Date: Fri, 20 Sep 2002 17:29:46 -0400	[thread overview]
Message-ID: <3D8B934A.1060900@wgate.com> (raw)
In-Reply-To: 3D8B8CAB.103C6CB8@digeo.com

Andrew Morton wrote:
> Michael Sinz wrote:
> 
>>coredump name format control via sysctl
>>
>>Provides for a way to securely move where core files show up and to
>>set the name pattern for core files to include the UID, Program,
>>Hostname, and/or PID of the process that caused the core dump.
> 
> 
> That seems a reasonable thing to want to do.
> 
> 
>>...
>>The following format options are available in that string:
>>
>>       %P   The Process ID (current->pid)
>>       %U   The UID of the process (current->uid)
>>       %N   The command name of the process (current->comm)
>>       %H   The nodename of the system (system_utsname.nodename)
>>       %%   A "%"
>>
>>For example, in my clusters, I have an NFS R/W mount at /coredumps
>>that all nodes have access to. The format string I use is:
>>
>>        sysctl -w "kernel.core_name_format=/coredumps/%H-%N-%P.core"
>>
> 
> 
> Does it need to be this fancy?  Why not just have:
> 
>         if (core_name_format is unset)
>                 use "core"
>         else
>                 use core_name_format/nodename-uid-pid-comm.core
> 
> which saves all that string format processing, while giving
> people everything they could want?

Well, it depends on if you really need the complex form or not.

There are some people who use a format of:

	%N.%P.core

which places the core file in the current directory but adds in the
name of the program.  (Something that is very nice when you have
a lot of programs that may core "together" when something bad happens)

The string processing is not that much work anyway (very small)
and, given the fact that I am about to write to disk a core dump,
it can not be a critical path/fast path issue either :-)

What can be done at the default pattern level in later kernels
would be to make it a bit more than just "core" (such as maybe
the "%N.%P.core" or something like that) but that is not that
complex.

Also, FreeBSD (yes, I know, it is not Linux) has a very simular
feature that we used for the FreeBSD clusters we built.

-- 
Michael Sinz -- Director, Systems Engineering -- Worldgate Communications
A master's secrets are only as good as
	the master's ability to explain them to others.



  reply	other threads:[~2002-09-20 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 20:40 [PATCH] kernel 2.4.19 & 2.5.38 - coredump sysctl Michael Sinz
2002-09-20 20:59 ` Andrew Morton
2002-09-20 21:01 ` Andrew Morton
2002-09-20 21:29   ` Michael Sinz [this message]
2002-09-20 21:50     ` Andrew Morton
2002-09-20 21:53     ` Andrew Morton
2002-09-20 23:32       ` Michael Sinz
2002-09-22 19:02   ` Bill Davidsen
2002-09-22 23:59     ` Andrew Morton
2002-09-23 19:00     ` Michael Sinz
     [not found] <3D8B87C7.7040106@wgate.com.suse.lists.linux.kernel>
     [not found] ` <3D8B8CAB.103C6CB8@digeo.com.suse.lists.linux.kernel>
     [not found]   ` <3D8B934A.1060900@wgate.com.suse.lists.linux.kernel>
     [not found]     ` <3D8B982A.2ABAA64C@digeo.com.suse.lists.linux.kernel>
2002-09-20 23:12       ` Andi Kleen
2002-09-20 23:27         ` Andrew Morton
2002-09-20 23:47           ` Andi Kleen
2002-09-21 20:19             ` Francois Romieu

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=3D8B934A.1060900@wgate.com \
    --to=msinz@wgate.com \
    --cc=akpm@digeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mks@sinz.org \
    --cc=riel@conectiva.com.br \
    --cc=rml@tech9.net \
    /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.