From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Schinker <ba1020@homie.homelinux.net>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16
Date: Tue, 25 Oct 2016 10:42:14 +0100 [thread overview]
Message-ID: <20161025094214.GS30231@citrix.com> (raw)
In-Reply-To: <390017287.340.1477334980049.JavaMail.zimbra@homie.homelinux.net>
On Mon, Oct 24, 2016 at 07:49:40PM +0100, Juergen Schinker wrote:
>
>
> > There is one called xenstored.service.
> >
> >> is xenstore supposed to start just because it is systemd enabled?
> >>
> >
> > I think so -- when you configure it properly when building Xen, those
> > files will be properly installed to the desired location of your test
> > host. Make sure you have systemd development package(s) installed on
> > your build host.
> >
> > My limited experience with those script shows that they work just fine.
> > I don't remember making any special adjustment to them.
> >
> > Wei.
>
> well this is what I get
>
> root@xen:~# systemctl enable xenstored
> Created symlink /etc/systemd/system/multi-user.target.wants/xenstored.service → /usr/local/lib/systemd/system/xenstored.service.
> The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
> settings in the [Install] section, and DefaultInstance for template units).
> This means they are not meant to be enabled using systemctl.
I don't follow.
Doesn't xenstored.service have "WantedBy=multi-user.target"?
> Possible reasons for having this kind of units are:
> 1) A unit may be statically enabled by being symlinked from another unit's
> .wants/ or .requires/ directory.
> 2) A unit's purpose may be to act as a helper for some other unit which has
> a requirement dependency on it.
> 3) A unit may be started when needed via activation (socket, path, timer,
> D-Bus, udev, scripted systemctl call, ...).
> 4) In case of template units, the unit is meant to be enabled with some
> instance name specified.
> root@xen:~# systemctl status xenstored
> ● xenstored.service - The Xen xenstore
> Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled)
> Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 5h ago
> Main PID: 1141 (code=exited, status=0/SUCCESS)
> CGroup: /system.slice/xenstored.service
^ no more output after this?
I have:
Main PID: 908 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/xenstored.service
└─972 /usr/local/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-25 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 20:04 Test Xen 4.8 RC3 FULL SUCCESS 21.10.16 Pry Mar
2016-10-24 13:14 ` Juergen Schinker
2016-10-24 13:27 ` Wei Liu
2016-10-24 17:57 ` Juergen Schinker
2016-10-24 18:16 ` Wei Liu
2016-10-24 18:49 ` Juergen Schinker
2016-10-25 9:42 ` Wei Liu [this message]
2016-10-25 12:55 ` Juergen Schinker
2016-10-25 13:22 ` Wei Liu
2016-10-24 19:42 ` Pry Mar
-- strict thread matches above, loose matches on Subject: below --
2016-10-21 21:27 Juergen Schinker
2016-10-26 16:09 ` Dario Faggioli
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=20161025094214.GS30231@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ba1020@homie.homelinux.net \
--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.