> 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. 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
