From: Louis Bouchard <louis.bouchard@hp.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Presentation of crashdc
Date: Fri, 03 Dec 2010 14:01:39 +0100 [thread overview]
Message-ID: <4CF8EA33.30705@hp.com> (raw)
Hello everyone
I just want to take a few minutes of your time to let you know about
crashdc, a project that I have been working on for the last year.
It is a set of scripts that leverage kexec's kdump_post mechanism to
generate a text file called crash-data-{date}.txt containing some
specific 'crash' command output.
This allows kexec to automatically generate a high level text file that
can be sent to support engineers without going through the pain of
sending multi-gigabyte files over the Internet.
crashdc can also be triggered by an initscript upon reboot if sysadmins
prefer to avoid execution of crash commands in the kexec booted kernel
context, as it sometimes require a sensible increase in the
crashkernel's reserved memory.
It is currently working on RHEL5, SLES10 and SLES11 and I'm working on
RHEL6 enablement (x86 and x86_64).
You can find more details about it here :
http://cariblog.kamikamamak.com/2009/10/17/crashdc-the-architecture/
The project is hosted here :
http://crashdc.sourceforge.net
If some of you are insterested in more details, don't hesitate to let me
know.
Kind Regards,
--
Louis Bouchard
Linux Support Engineer
Team lead, EMEA Linux Competency Center,
Linux Advocate, HP
HP Technology Services - Global Competency Center
Hewlett-Packard Company
louis.bouchard@hp.com / Email
Mon-Fri 9-17<WET>,<GMT+2> / Working Hours
Mark Fay / Manager
mark.fay@hp.com / Manager's Email
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2010-12-03 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CF8EA33.30705@hp.com \
--to=louis.bouchard@hp.com \
--cc=kexec@lists.infradead.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