From: Ian Campbell <ian.campbell@citrix.com>
To: Ting-Wei Lan <lantw44@gmail.com>, xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] build: use correct qemu path in systemd service file and init script
Date: Mon, 27 Jul 2015 08:59:23 +0100 [thread overview]
Message-ID: <1437983963.28924.19.camel@citrix.com> (raw)
In-Reply-To: <55B3B720.8030601@gmail.com>
On Sun, 2015-07-26 at 00:19 +0800, Ting-Wei Lan wrote:
> Ian Campbell 於 西元2015年07月24日 16:57 寫道:
>
> > I think if $withval is yes and we are converting that to "qemu" then
> > QEMU_XEN_PATH should just be "qemu" and we should substitute that in
> > the initscript too. IOW the "taken from $PATH" applies just as much to
> > the initscript usage as it does to the toolstack.
>
> Yes, we can use "qemu" in init scripts, but systemd service files
> require absolute paths. We still have to do different things such as
> "/usr/bin/env qemu" for systemd.
That's fine, IMHO systemd induced oddness ought to be confined to
systemd specific places.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-27 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 16:15 [PATCH] build: use correct qemu path in systemd service file and init script Ting-Wei Lan
2015-07-16 16:30 ` Andrew Cooper
2015-07-16 16:58 ` Ting-Wei Lan
2015-07-21 15:10 ` Ian Campbell
2015-07-23 17:38 ` Ting-Wei Lan
2015-07-24 8:57 ` Ian Campbell
2015-07-25 16:19 ` Ting-Wei Lan
2015-07-27 7:59 ` Ian Campbell [this message]
2015-07-30 6:51 ` [PATCH v2] " Ting-Wei Lan
2015-07-30 10:24 ` Ian Campbell
2015-07-30 10:30 ` Wei Liu
2015-07-30 15:01 ` Ian Campbell
2015-07-30 18:21 ` Ting-Wei Lan
2015-07-30 11:23 ` Anthony PERARD
2015-07-30 11:35 ` Ian Campbell
2015-07-30 15:44 ` Doug Goldstein
2015-07-31 9:13 ` Wei Liu
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=1437983963.28924.19.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=lantw44@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.