All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>, Wei Liu <wei.liu2@citrix.com>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	Doug McMillan <dlm1065@hotmail.com>,
	xen-devel <xen-devel@lists.xen.org>,
	"xen-users@lists.xenproject.org" <xen-users@lists.xenproject.org>
Subject: Re: [Xen-users] [TestDay] minor bug + possible configuration bug 4.5rc4 archlinux
Date: Tue, 13 Jan 2015 15:30:00 +0000	[thread overview]
Message-ID: <1421163000.19103.114.camel@citrix.com> (raw)
In-Reply-To: <21685.13757.675710.628234@mariner.uk.xensource.com>

On Tue, 2015-01-13 at 15:11 +0000, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-users] [TestDay] minor bug + possible configuration bug 4.5rc4 archlinux"):
> > On Tue, 2015-01-13 at 09:45 +0100, Olaf Hering wrote:
> > > I dont think we can do anything about this systemd brain damage. Either
> > > it gets its Where= from such line within the file, or it gets its Where=
> > > from the filename. In which case it has to stop looking at a Where=
> > > line.
> > 
> > We either need to make XEN_LIB_STORED be hardcoded to /var/lib/xenstored
> > (i.e. ignoring localstatedir) or we need to make the systemd units
> > reflect the --localstatedir the user provided or we need to remove
> > --localstatedir as a user selectable option.
> > 
> > (the first is probably easiest, the second is probably more correct and
> > the third seems like overkill to me)
> 
> The first and third are imposing systemd-originated brokenness on
> non-systemd users and are therefore not really acceptable.

Given that I think my preference would be for my second option.

> There is a fourth option: we arrange that if the user specifies
> --localstatedir it still breaks with systemd, but perhaps that they
> get an error message earlier.  That confines the systemd breakage to
> systemd users.

Or Five: hardcode /var/lib/xenstored for systemd only (i.e. ignore
XEN_LIB_STORED).

Ian.

  reply	other threads:[~2015-01-13 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <COL130-W76677AD7735CFF5C73D568A8450@phx.gbl>
2015-01-12 14:58 ` [Xen-users] [TestDay] minor bug + possible configuration bug 4.5rc4 archlinux Ian Campbell
2015-01-12 16:00   ` Wei Liu
2015-01-12 16:17   ` Olaf Hering
2015-01-13  0:36     ` Doug McMillan
2015-01-13  7:47       ` Olaf Hering
2015-01-13  8:45   ` Olaf Hering
2015-01-13 10:24     ` Ian Campbell
2015-01-13 15:11       ` Ian Jackson
2015-01-13 15:30         ` Ian Campbell [this message]
2015-01-14  3:55     ` Doug McMillan
2015-01-14  7:46       ` Olaf Hering

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=1421163000.19103.114.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dlm1065@hotmail.com \
    --cc=mcgrof@suse.com \
    --cc=olaf@aepfle.de \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@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 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.