Re: [PATCH v3 7/7] systemd: add support initial xen systemd service files

["Luis R. Rodriguez" <mcgrof@do-not-panic.com>]

On Thu, Mar 20, 2014 at 1:53 PM, M A Young <m.a.young@durham.ac.uk> wrote:
> I have not read through this fully, but xenstored.service and
> oxenstored.service need an additional line like
> ExecStartPost=-/usr/bin/xenstore-write "/local/domain/0/domid" 0
> for xen 4.4 and later.

It was there for both, but now that I look at it I had only made this
optional to fail on oxenstore. The init script lets it fail so I
suppose letting it fail on both is OK, but perhaps its a good time to
think about if we want to allow that to fail.

While doing some more testing another thing I noticed was that the
trick I was expecting to work of having
xen-qemu-dom0-disk-backend.service.in to Require xenstored.socket
instead of either xenstored.service or oxenstored.service doesn't cut
it, even if we explicitly claim the socket within the store services.
Let me know if anyone sees a away to use logic within systemd to make
a service exclusively through sockets for services that provide their
own ExecStart but just don't see it now. If we can't find a way that
may mean we either have to write our own wrapper C program to check
for both or have this configurable upon build. As for the later I at
least don't get oxenstored being built by default, even though it
seems I probably should as that is the way of the future, so we'd have
to just lave the C xenstored as the default for now I guess.

  Luis