From 631b676bb7636971c2e1c42528f49378d8970696 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 24 Nov 2016 18:47:48 +0100 Subject: core: explicitly verify that BindsTo= deps are in order before dispatch start operation of a unit Let's make sure we verify that all BindsTo= are in order before we actually go and dispatch a start operation to a unit. Normally the job queue should already have made sure all deps are in order, but this might not have been sufficient in two cases: a) when the user changes deps during runtime and reloads the daemon, and b) when the user placed BindsTo= dependencies without matching After= dependencies, so that we don't actually wait for the bound to unit to be up before upping also the binding unit. See: #4725 --- NEWS | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'NEWS') diff --git a/NEWS b/NEWS index ec50c0c403..23f555fc53 100644 --- a/NEWS +++ b/NEWS @@ -35,6 +35,10 @@ CHANGES WITH 233 in spe names of remote hosts and to reply to mDNS's A and AAAA requests from the hosts. + * When units are about to be started an additional check is now done to + ensure that all dependencies of type BindsTo= (when used in + combination with After=) have been started. + CHANGES WITH 232: * The new RemoveIPC= option can be used to remove IPC objects owned by -- cgit v1.2.3-54-g00ecf