public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] core file naming option
Date: Mon, 8 Oct 2001 17:32:14 -0400	[thread overview]
Message-ID: <20011008173214.A19007@disaster.jaj.com> (raw)

After seeing this topic in the Kernel Cousin and reading through the mail
archives, I thought I'd mention a very useful feature that Linux could
steal^H^H^H^H^Hleverage from Solaris:  the coreadm(1) program allows users
to set a pattern for core file names, e.g.,

    /var/core/core.%f.%p

for command foo with pid 1234 dumps core in /var/core/core.foo.1234 (to
use the example from the coreadm man page).  There're about half a dozen
% patterns.

The root user can set patterns and policies systemwide (e.g., no coredumps
for regular users, dump all corefiles everywhere into a directory readable
only by root, etc, for security reasons).  Also, this pattern information
is stored per-process AFAICT, so in my login files I have

    coreadm -p core.%f.%p $$

Meaning that all core files go into the current directory.  It gets set
for the shell itself, and all the processes spawned from that shell.

Both as a user and a sysadmin, I've found this to be very very useful.


Anyhow, just a thought.  Thanks for reading.

Luck++;
Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

             reply	other threads:[~2001-10-08 21:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 21:32 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2001-09-27 16:17 ` bill davidsen
2001-09-27 17:09   ` Eli Carter

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=20011008173214.A19007@disaster.jaj.com \
    --to=pedwards@disaster.jaj.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