On Fri, 13.07.12 16:19, Michal Sekletar ([email protected]) wrote:
>
> On Tue, 2012-07-10 at 00:54 +0200, Lennart Poettering wrote:
> > Can you elaborate on this? Would generators work for you?
> >
> > http://www.freedesktop.org/wiki/Software/systemd/Generators
> >
> > (Sorry for not respondi
On Tue, 2012-07-10 at 00:54 +0200, Lennart Poettering wrote:
> Can you elaborate on this? Would generators work for you?
>
> http://www.freedesktop.org/wiki/Software/systemd/Generators
>
> (Sorry for not responding earlier!)
>
> Lennart
>
Hi Lennart,
I'd like to work on this, because I think
'Twas brillig, and Lennart Poettering at 09/07/12 23:54 did gyre and gimble:
> On Mon, 25.06.12 09:43, Michal Sekletar ([email protected]) wrote:
>
>> Another feature which systemd currently doesn't support and it's
>> closely related to previous issues, is starting instances based on
>> configu
On Mon, 25.06.12 09:43, Michal Sekletar ([email protected]) wrote:
> Another feature which systemd currently doesn't support and it's
> closely related to previous issues, is starting instances based on
> configuration. There should be an option to enable a behavior, when
> instances of template
On Mon, 2012-06-25 at 09:43 +0200, Michal Sekletar wrote:
> Also it should be possible to group more instances together
> and control them as a group. In such case template service will
> contain WantedBy= option, where some other target should be specified,
> e.g. opevpn.target. However, instance
Hello everyone out there,
We would like to start a discussion about a way how should systemd deal
with template units, because we consider current state as not sufficient
to meet all use cases very often seen in server administration.
Consider a scenario where administrator has a lot of instances
