From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Maciej Borzęcki" <maciej.borzecki@rndity.com>
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: Wed, 7 Dec 2016 08:37:38 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1612070835310.2008@ca624034.mitel.com> (raw)
In-Reply-To: <CAD4b0_+EACruAvA839=YTu8=FHAjGcuMzFbaLugJZQD6NOjf2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
On Tue, 6 Dec 2016, Maciej Borzęcki 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).
already looking into that ... is it safe to say that RH's "abrt" is,
well, exclusive to RH?
and pretty sure i asked this before ... is there some reasonable
equivalent to "sosreport" for OE?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-12-07 13:39 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
2016-12-07 13:37 ` Robert P. J. Day [this message]
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=alpine.LFD.2.20.1612070835310.2008@ca624034.mitel.com \
--to=rpjday@crashcourse.ca \
--cc=maciej.borzecki@rndity.com \
--cc=openembedded-core@lists.openembedded.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