Bug#727708: init multiple instances of a daemon

[Tollef Fog Heen <tfheen@err.no>]

]] Russ Allbery 

> Daniel Pocock <daniel@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.

The ideomatic systemd way seems to be to use a target for it.  Take a
look at how getty.target works, for instance.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are