mesh/delivery held for a person: merged without a passing check: only a person decides what follows
mesh/check pass 91d041b62a1a on ec76ab77c058 | unit 163 run, 421 kept | integration 173 run, 487 kept | over bound: integration (slowest integration m…
systemd-resolved, held on shanks by the operator under rule 2, was raised as an urgent "on no list" condition and reminded every hour, although its hold is already said and answered on the held list. A node now goes on neither list only when it gets no want and the module is not held, by a hold read at its fingerprint or one this pass raises. The first pass after a start clears the neither condition of every assigned node not on neither list, not only those with a want, so a neither raised before the restart for a held module (or a move waiting for its record ask) is cleared too.