All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:22:52 +0100	[thread overview]
Message-ID: <20161025132252.GX30231@citrix.com> (raw)
In-Reply-To: <1712938885.573.1477400114751.JavaMail.zimbra@homie.homelinux.net>

On Tue, Oct 25, 2016 at 01:55:14PM +0100, Juergen Schinker wrote:
>  
> > 
> > Doesn't xenstored.service have "WantedBy=multi-user.target"?
> > 
> 
> /usr/local/lib/systemd/system/xenstored.service
> 
> [Unit]
> Description=The Xen xenstore
> Requires=proc-xen.mount var-lib-xenstored.mount
> After=proc-xen.mount var-lib-xenstored.mount
> Before=libvirtd.service libvirt-guests.service
> RefuseManualStop=true
> ConditionPathExists=/proc/xen/capabilities
> 
> [Service]
> Type=notify
> NotifyAccess=all
> RemainAfterExit=true
> ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities
> ExecStart=/etc/xen/scripts/launch-xenstore
> 
> [Install]
> WantedBy=multi-user.target
> Also=proc-xen.mount
> Also=var-lib-xenstored.mount

This looks right.

> 
> 
> >> 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
>  
> No more thats it
> 
>  
> hm this is status today and I haven;t rebootet but remember I started the service by hand
> 
> 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 23h ago
>  Main PID: 1141 (code=exited, status=0/SUCCESS)
>     Tasks: 0 (limit: 4915)
>    CGroup: /system.slice/xenstored.service
> 
> Oct 23 14:41:15 xen systemd[1]: Starting The Xen xenstore...
> Oct 23 14:41:15 xen systemd[1]: Started The Xen xenstore.

I don't see there is any error. I'm no systemd expert though.

Wei.

> root@xen:~# 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-10-25 13:22 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
2016-10-25 12:55             ` Juergen Schinker
2016-10-25 13:22               ` Wei Liu [this message]
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=20161025132252.GX30231@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.