Daniel Pocock <dan...@pocock.com.au> writes: > Just to clarify: does this mean systemd and upstart can refer to the > instances collectively or individually as required? E.g. you can tell > it restart all instances of httpd (on dpkg upgrade) or just restart one > specific instance (after a config change)?
It looks like both upstart and systemd don't provide direct mechanisms to manage all instances. The upstart cookbook recommends getting a list of all active services and extracting the list of instances of a particular service from that, and then acting on them in a loop. systemd's docs (at least that I can find) don't have a similar recipe, but systemd has all the tools required to do the same thing. > Will additional effort be needed so that dpkg or maintainer scripts can > request the collective restart of all instances, Yes. > should this be documented with a wishlist bug against dpkg perhaps? I would hold off until we decide which init system we're going with, and I'm not sure where this belongs. It may make more sense to put it into dh-systemd and/or dh_installinit. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wqiwvcgg....@windlord.stanford.edu
