Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: "Maciej Borzęcki" <maciej.borzecki@rndity.com>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: what is the closest alternative to red hat's ABRT in OE?
Date: Tue, 6 Dec 2016 17:59:30 -0500	[thread overview]
Message-ID: <879b42db-266b-f662-bb06-b8043dca08a5@windriver.com> (raw)
In-Reply-To: <CAD4b0_+EACruAvA839=YTu8=FHAjGcuMzFbaLugJZQD6NOjf2Q@mail.gmail.com>

On 2016-12-06 11:02 AM, Maciej BorzD\x19cki wrote:
> On Tue, Dec 6, 2016 at 3:49 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>>
>>   as in:
>>
>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-abrt.html
>>
>> specifically, to manage core files? i would have thought judicious use
>> of "ulimit" would be the solution. others?
>>
>
> If you're using systemd there is systemd-coredump(8).
>

You could try minicoredumper:

https://linutronix.de/minicoredumper/

<quote>
    The minicoredumper project provides a program that handles the
    creation of core dump files on Linux. It can produce much smaller
    core dump files by making use of sparse files, compression, and
    allowing the user to configure what parts of the process memory
    image should be dumped.
</quote>

There's even a slightly out of date meta-oe recipe:

http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-oe/recipes-kernel/minicoredumper/minicoredumper_1.0.2.bb?h=master


Oh and Ubuntu uses apport:
   https://wiki.ubuntu.com/Apport

	--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5


  reply	other threads:[~2016-12-06 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 14:49 what is the closest alternative to red hat's ABRT in OE? Robert P. J. Day
2016-12-06 16:02 ` Maciej Borzęcki
2016-12-06 22:59   ` Randy MacLeod [this message]
2016-12-07 13:37   ` Robert P. J. Day
2016-12-07 13:43     ` Burton, Ross

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=879b42db-266b-f662-bb06-b8043dca08a5@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=maciej.borzecki@rndity.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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