From: "Jan Rękorajski" <baggins@pld-linux.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jacek Konieczny <jajcus@jajcus.net>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] systemd: add support initial systemd service files
Date: Wed, 12 Mar 2014 12:24:01 +0100 [thread overview]
Message-ID: <20140312112400.GA12300@sith.mimuw.edu.pl> (raw)
In-Reply-To: <CAB=NE6U13jj3sPQRUZwdp7FW-cL9j8+GOuE=biL-XJZTosJh7Q@mail.gmail.com>
On Wed, 12 Mar 2014, Luis R. Rodriguez wrote:
> On Wed, Mar 12, 2014 at 2:07 AM, Jacek Konieczny <jajcus@jajcus.net> wrote:
> >
> > This is what we have inPLD Linux (currently for Xen 4.3.2), probably
> > based on work from some other distro (Fedora, I guess):
> >
> > https://github.com/pld-linux/xen/blob/master/xen-watchdog.service
> > https://github.com/pld-linux/xen/blob/master/xenconsoled.service
> > https://github.com/pld-linux/xen/blob/master/xendomains.service
> > https://github.com/pld-linux/xen/blob/master/xenstored.service
> >
> > It may be not perfect, nor ready for inclusion in the upstream Xen,
> > but I think this is the way to go. They may also need updates for
> > current Xen.
>
> Thanks, I'll test and study these. If they are better then great. My
> main issue is seeing evolution happening anywhere not upstream and Xen
> doesn't need anymore of it.
>
> >> Seems like you can provide a much better set of suitable scripts, mind
> >> just taking them and fixing them or would you like me to take your
> >> advice steps by step?
> >
> > Feel free to take those scripts. Unfortunately, I won't be able to
> > prepare a ready patch for Xen by myself.
> >
> > Cc: Jan Rękorajski, who committed the first version of our systemd units.
>
> Jan, where did these come from?
The service files as such I took from Fedora, but the xendomains.sh
script used by the service is a slight modification of Debian's, because
I wanted our packages to support both xm and xl toolstacks.
I'm using them on my production servers without any problems.
--
Jan Rękorajski | PLD/Linux
SysAdm | http://www.pld-linux.org/
baggins<at>mimuw.edu.pl
baggins<at>pld-linux.org
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-12 11:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 0:03 [PATCH] systemd: add support initial systemd service files Luis R. Rodriguez
2014-03-12 8:16 ` Jacek Konieczny
2014-03-12 8:35 ` Luis R. Rodriguez
2014-03-12 9:07 ` Jacek Konieczny
2014-03-12 9:19 ` Luis R. Rodriguez
2014-03-12 11:24 ` Jan Rękorajski [this message]
2014-03-12 11:22 ` Ian Campbell
2014-03-12 19:44 ` M A Young
2014-03-12 23:43 ` Luis R. Rodriguez
2014-03-13 0:37 ` M A Young
2014-03-12 23:53 ` Luis R. Rodriguez
2014-03-13 0:01 ` M A Young
2014-03-13 0:06 ` Luis R. Rodriguez
2014-03-13 8:03 ` Jacek Konieczny
2014-03-13 9:52 ` Ian Campbell
2014-03-13 9:55 ` Jacek Konieczny
2014-03-12 11:14 ` Ian Jackson
2014-03-12 11:25 ` Ian Campbell
2014-03-12 11:42 ` Andrew Cooper
2014-03-12 18:35 ` Luis R. Rodriguez
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=20140312112400.GA12300@sith.mimuw.edu.pl \
--to=baggins@pld-linux.org \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jajcus@jajcus.net \
--cc=mcgrof@do-not-panic.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).