Re: Antw: [EXT] Re: User/Group overrides in a templated service triggered via timer

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mo, 07.09.20 14:19, Kevin P. Fleming (kevin@xxxxxxx) wrote:

> On Mon, Sep 7, 2020 at 11:58 AM Lennart Poettering
> <lennart@xxxxxxxxxxxxxx> wrote:
> > Not sure I can parse this. Both timers and services are units in
> > systemd. You can enable timer units, and you can enable service units,
> > it all depends on what you put in their [Install] section. Sometimes
> > it makes sense to add an [Install] section to one, sometimes to the
> > other, sometimes to both, dependning on what the triggers should be
> > that you want to use. Pretty often it might make sense to include just
> > an Also=foobar.timer in the [Install] section of foobar.service, which
> > then means that if the service is enabled, foobar.timer is enabled
> > implicitly.
>
> Hindsight being 20/20, it would probably have made more sense to users
> if the command was 'systemctl install' since that would match the
> section name in the unit file. It's a bit late for that now :-)

It actually was named like that originally, a long long time ago.

We nowadays use "install" as generic terminology for "enable",
"disable", "mask" and so on, i.e. for any form of hooking stuff in or
out.



Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel