Per the discussion in [0], the hard-coded pid file can be removed completely. Systemd has no trouble figuring out the pid of devd all by itself.
[0]: https://lists.xen.org/archives/html/xen-devel/2016-07/msg01393.html Signed-off-by: Wei Liu <wei.l...@citrix.com> --- Cc: Ian Jackson <ian.jack...@eu.citrix.com> Cc: Rusty Bird <rustyb...@openmailbox.org> --- tools/hotplug/Linux/systemd/xendriverdomain.service.in | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/tools/hotplug/Linux/systemd/xendriverdomain.service.in b/tools/hotplug/Linux/systemd/xendriverdomain.service.in index c0cd454..85972b5 100644 --- a/tools/hotplug/Linux/systemd/xendriverdomain.service.in +++ b/tools/hotplug/Linux/systemd/xendriverdomain.service.in @@ -7,8 +7,7 @@ ConditionVirtualization=xen [Service] Type=forking -ExecStart=@sbindir@/xl devd --pidfile=/var/run/xldevd.pid -PIDFile=/var/run/xldevd.pid +ExecStart=@sbindir@/xl devd [Install] WantedBy=multi-user.target -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
