Re: Bug#727708: init multiple instances of a daemon
On 23/12/13 08:41, Adrien Clerc wrote:
> Le 23/12/2013 00:37, Zbigniew Jędrzejewski-Szmek a écrit :
>>> 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
>>
> This could be controlled via a setting inside the unit file, like
> AllowGlobControl, default set to false in template unit files.
>
Going back to the SysVinit world for a moment... maybe we could add an
extra keyword in the LSB data in the init scripts, e.g.
X-Package: apache2
would indicate that an init script is based on the apache2 package and
should be executed whenever the primary init script from the package is
executed by the maintainer scripts
When people copy the apache2 init script or make any of their own custom
init scripts using binaries from the apache2 package, they would have to
make sure that line is included in their new script
Reply to: