public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Sinz <msinz@wgate.com>
To: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Core dump file control
Date: Sun, 17 Feb 2002 09:36:07 -0500	[thread overview]
Message-ID: <3C6FBFD7.238F8915@wgate.com> (raw)
In-Reply-To: <200202161737.g1GHbkJh001254@tigger.cs.uni-dortmund.de>

Horst von Brand wrote:
> 
> Michael Sinz <msinz@wgate.com> said:
> > I have, for a long time, wished that Linux had a way to specify where
> > core dumps are stored
> 
> CWD (chdir(2))

So, all of my applications and support programs should run with their
CWD set to /coredumps?  I don't want to flame here, but "get real".

That is almost as good as saying that to get security you just need to
make sure no one bad is using your system.

> >                       and what the name of the core dump is.
> 
> /proc/sys/kernel/core_uses_pid

Well, this does make unique file names, almost.  But it does not really
identify the file.  Plus, in a cluster of machines, many of them have
the same PIDs.  (Say, 100 machines, you get 100 of each PID)

-- 
Michael Sinz ---- Blackdown Java -- http://www.sinz.org/Michael.Sinz
Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com
A master's secrets are only as good as
	the master's ability to explain them to others.

  reply	other threads:[~2002-02-17 14:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 17:57 [PATCH] Core dump file control Michael Sinz
2002-02-15 19:07 ` Michael Sinz
2002-02-16 17:37 ` Horst von Brand
2002-02-17 14:36   ` Michael Sinz [this message]
     [not found] <361c88b8047e6c07d2@[192.168.1.4]>
2002-02-14 17:53 ` Michael Sinz
     [not found] <3C6BE18F.7B849129@wgate.com.suse.lists.linux.kernel>
2002-02-14 16:37 ` Andi Kleen
     [not found] ` <363c044a047f1f07d2@[192.168.1.4]>
2002-02-14 17:09   ` Michael Sinz
  -- strict thread matches above, loose matches on Subject: below --
2002-02-14 16:10 Michael Sinz
2002-02-15 11:40 ` Jakob Østergaard
2002-02-15 11:44   ` Martin Dalecki
2002-02-15 12:11     ` Michael Sinz
2002-02-15 12:13     ` Jakob Østergaard
2002-02-15 12:22       ` Martin Dalecki
2002-02-15 12:32         ` Jakob Østergaard
2002-02-15 12:55         ` Michael Sinz
2002-02-15 12:06   ` Michael Sinz

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=3C6FBFD7.238F8915@wgate.com \
    --to=msinz@wgate.com \
    --cc=brand@jupiter.cs.uni-dortmund.de \
    --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