From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, dledford@redhat.com, harald@redhat.com
Subject: [PATCH 0/2] add support for launching mdmon via systemd
Date: Fri, 18 Jan 2013 09:43:10 +0100 [thread overview]
Message-ID: <1358498592-20827-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Hi,
It's been an ongoing issue for a while trying to figure out how to
handle launching mdmon from the initrd in Fedora and avoid it getting
killed by systemd due to it ending up in the wrong cgroup (udev).
We tried simply attaching mdmon to the cgroup of systemd but it didn't
really work, and in the end it seems to be more in line with the
systemd mentality to have systemd spawn it. With these patches and a
few pending changes to dracut, I am finally able to boot and reboot
systems with 1 or 2 IMSM arrays.
The patch for systemctl is implemented as a compile time option rather
than a command line option, since I think it is something that the
distro will decide. However we can make it a command line option if
preferred.
I also have matching systemd .service files for this, which I am happy
to contribute, but I am not sure if they are useful to other distros
or not? We haven't had a history of including .service files with
mdadm.
Cheers,
Jes
Jes Sorensen (2):
Add support for launching mdmon via systemctl instead of fork/exec
execl() only returns in case of error
Makefile | 6 ++++++
mdmon.c | 4 +++-
util.c | 15 ++++++++++++++-
3 files changed, 23 insertions(+), 2 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-01-18 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 8:43 Jes.Sorensen [this message]
2013-01-18 8:43 ` [PATCH 1/2] Add support for launching mdmon via systemctl instead of fork/exec Jes.Sorensen
2013-01-18 8:43 ` [PATCH 2/2] execl() only returns in case of error Jes.Sorensen
2013-01-18 9:02 ` [PATCH 0/2] add support for launching mdmon via systemd NeilBrown
2013-01-18 9:09 ` Jes Sorensen
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=1358498592-20827-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=dledford@redhat.com \
--cc=harald@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).