Re: Bug#727708: init multiple instances of a daemon
On Sun, Dec 22, 2013 at 12:48:47PM -0800, Russ Allbery wrote:
> upstart calls this "instances" and systemd calls this "unit
> templates".
We too call them instances: an instance is created from a template.
> 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.
That's true (I'm only speaking about systemd). There have been requests for
such functionality before, but nothing was implemented. But I think we should
revisit this topic... I recently added globbing to a bunch of systemctl verbs
for listing stuff (list-units, list-sockets, etc.), and it was actually
trivial. I felt that allowing globing for verbs that influence state (start,
stop, enable, disable, ...) was too dangerous. But this should be safe for
instance units, so I'd like to see 'systemctl stop/status/... server@*.service'
implemented.
Zbyszek
Reply to: