xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Konieczny <jajcus@jajcus.net>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	M A Young <m.a.young@durham.ac.uk>
Cc: ehouby@yahoo.com, xen@lists.fedoraproject.org, xen-devel@lists.xen.org
Subject: Re: [TestDay] xen 4.4 FC3 xl create error
Date: Wed, 05 Feb 2014 14:32:50 +0100	[thread overview]
Message-ID: <52F23D82.2060306@jajcus.net> (raw)
In-Reply-To: <1391592517.6497.76.camel@kazak.uk.xensource.com>

On 02/05/14 10:28, Ian Campbell wrote:
> On Tue, 2014-02-04 at 18:41 +0000, M A Young wrote:
>>> We should probably consider taking some unit files into the xen tree, if
>>> someone wants to submit a set?
>>
>> I can submit a set, which start services individually rather than a 
>> unified xencommons style start file. I didn't find a good way to reproduce 
>> the xendomains script, so I ended running an edited version of the 
>> sysvinit script with a systemd wrapper file.
> 
> I don't know what is conventional in systemd land but I have no problem
> with that approach.

For systemd the much more natural way is to start and monitor each
daemon with
a separate systemd unit. If some extra scripting is needed (like the
setting xenstore values for dom0), that should be coded in a separate
script and one of the two:

– Called via ExecStartPre or ExecStartPost in the unit of the daemon the
scripting is for (e.g. filling xenstore would go to ExecStartPost of
xenstored.service)
– Called via ExecStart in its own service unit.

Writing extra scripts may be not necessary when just a few commands
have to be started.

e.g. the xenstored.service from PLD Linux (based on some unit for xenstored
found on the Internet):

[Unit]
Description=Xenstored - daemon managing xenstore file system
Requires=proc-xen.mount var-lib-xenstored.mount
After=proc-xen.mount var-lib-xenstored.mount
Before=libvirtd.service libvirt-guests.service xendomains.service
xend.service
RefuseManualStop=true
ConditionPathExists=/proc/xen

[Service]
Type=forking
Environment=XENSTORED_ARGS=
Environment=XENSTORED_ROOTDIR=/var/lib/xenstored
EnvironmentFile=-/etc/sysconfig/xenstored
PIDFile=/var/run/xenstored.pid
ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities
ExecStartPre=-/bin/rm -f "$XENSTORED_ROOTDIR"/tdb*
ExecStart=/usr/sbin/xenstored --pid-file /var/run/xenstored.pid
$XENSTORED_ARGS
ExecStartPost=/usr/bin/xenstore-write "/local/domain/0/name" "Domain-0"

[Install]
WantedBy=multi-user.target

-- 
Greets,
  Jacek

  reply	other threads:[~2014-02-05 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 15:26 [TestDay] xen 4.4 FC3 xl create error Eric Houby
2014-02-04 16:12 ` Ian Campbell
2014-02-04 18:41   ` M A Young
     [not found]   ` <alpine.DEB.2.00.1402041828250.26392@procyon.dur.ac.uk>
2014-02-04 19:32     ` M A Young
2014-02-05  9:28     ` Ian Campbell
2014-02-05 13:32       ` Jacek Konieczny [this message]
2014-02-05 23:07       ` M A Young

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=52F23D82.2060306@jajcus.net \
    --to=jajcus@jajcus.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=ehouby@yahoo.com \
    --cc=m.a.young@durham.ac.uk \
    --cc=xen-devel@lists.xen.org \
    --cc=xen@lists.fedoraproject.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).