[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Test Xen 4.8 RC3 FULL SUCCESS 21.10.16


  • To: Wei Liu <wei.liu2@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Juergen Schinker <ba1020@xxxxxxxxxxxxxxxxxxx>
  • Date: Tue, 25 Oct 2016 13:55:14 +0100 (BST)
  • Delivery-date: Tue, 25 Oct 2016 12:55:45 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: 7XLCzwqBJWCAN3LwoYgTxduo9B1Cvw==
  • Thread-topic: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

 
> 
> 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


>> 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.
root@xen:~# 

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.