From: Louis Bouchard <louis.bouchard@canonical.com>
To: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: debian's kdump-tools migration to systemd
Date: Fri, 28 Nov 2014 16:14:09 +0100 [thread overview]
Message-ID: <54789141.4060602@canonical.com> (raw)
Hello everyone,
I understand that this is Thanksgiving weekend so not many american eyes will
see this but I still want to bounce the idea somewhere before uploading this to
Debian.
I recently realized that the kernel dump mechanism (kdump-tools) on debian was
broken, partly because of systemd and also because of a change of format of the
dmesg log. The later is fixed upstream but systemd is another issue.
Debian uses a sysVinit script called kdump-tools that setup kexec and prepare
things in case of a kernel panic. To make sure that a systemd enabled system
does not reach multi-user when a kernel panic triggers kexec to load the new
kernel, I am adding the following boot parameter :
systemd.unit=kdump-tools.service
The systemd kdump-tools.service unit calls the kdump-tools script that copies
the content of /proc/vmcore to local storage and then reboots the server.
The rest of the execution remain identical. Systems that will not be running
systemd will remain unchanged.
I would be happy to take comments and suggestion but keep in mind that I have
limited time until debian's final freeze which is dec 5th so I will proceed with
my debian upload before that.
Kind regards,
...Louis
--
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63 B9C4 8B3D 867C 823E 7A61
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2014-11-28 15:14 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=54789141.4060602@canonical.com \
--to=louis.bouchard@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.