xendomains init script; Add should-dependency on nfs-kernel-server

Perhaps the guests use the hosts's NFS server, as in the case reported
in #826871.

In any case, it seems much more likely that on a system which is an
NFS server and also a Xen host, that the guests depend on the NFS,
rather than vice versa.

The obvious exception would be a driver domain.  Driver domains
probably need to be handled separately anyway, since they must start
before other domains.  (And anyway they are not particularly
well-handled by the current packaging.)

Closes: #826871
Signed-off-by: Ian Jackson <ian.jackson@citrix.com>

diff --git a/debian/xen-utils-common.xendomains.init b/debian/xen-utils-common.xendomains.init
index 53457ce59780bac87c1a12c214976813ad5185ee..ca03ae4cfed9b2a4bf176f412de2dd4460079c96 100644 (file)
--- a/debian/xen-utils-common.xendomains.init
+++ b/debian/xen-utils-common.xendomains.init
@@ -3,8 +3,8 @@
 # Provides:          xendomains
 # Required-Start:    $syslog $network $remote_fs xen
 # Required-Stop:     $syslog $network $remote_fs xen
-# Should-Start:      drbd iscsi openvswitch-switch
-# Should-Stop:       drbd iscsi openvswitch-switch
+# Should-Start:      drbd iscsi openvswitch-switch nfs-kernel-server
+# Should-Stop:       drbd iscsi openvswitch-switch nfs-kernel-server
 # X-Start-Before:    corosync heartbeat libvirtd
 # X-Stop-After:      corosync heartbeat libvirtd
 # Default-Start:     2 3 4 5