init/FreeBSD: fix xencommons so it can only be launched by Dom0
authorRoger Pau Monne <roger.pau@citrix.com>
Mon, 19 Dec 2016 15:02:03 +0000 (15:02 +0000)
committerWei Liu <wei.liu2@citrix.com>
Wed, 21 Dec 2016 16:33:45 +0000 (16:33 +0000)
At the moment the execution of xencommons is gated on the presence of the
privcmd device, but that's not correct, since privcmd is available to all Xen
domains (privileged or unprivileged). Instead of using privcmd use the
xenstored device, which will only be available to the domain that's in charge
of running xenstored, and thus xencommons.

Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
tools/hotplug/FreeBSD/rc.d/xencommons.in

index efa88012bb03ec15e8a89b5ac56f5514c9052aca..81f69f387531e03314671c54962ccbf892c96c12 100644 (file)
@@ -16,7 +16,7 @@ start_cmd="xen_startcmd"
 stop_cmd="xen_stop"
 status_cmd="xen_status"
 extra_commands="status"
-required_files="/dev/xen/privcmd"
+required_files="/dev/xen/xenstored"
 
 XENSTORED_PIDFILE="@XEN_RUN_DIR@/xenstored.pid"
 XENCONSOLED_PIDFILE="@XEN_RUN_DIR@/xenconsoled.pid"