On Mo, 07.09.20 14:19, Kevin P. Fleming (ke...@km6g.us) wrote:
> On Mon, Sep 7, 2020 at 11:58 AM Lennart Poettering
> 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
On Mon, Sep 7, 2020 at 11:58 AM Lennart Poettering
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
On Mo, 07.09.20 10:00, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> > "Enabling" doesn't necessarily mean "start this at boot". Instead it
> > just means "start this at the hookpoints that are declared in the
> > unit's [Install] section". Typically this lists a hook point activated
On Mon, Sep 7, 2020 at 4:22 AM Reindl Harald wrote:
> a timer is the same trigger as "enable" and get startet as part of the
> boot process
>
> * letsencrypt.timer
> * letsencrypt.service
>
> letsencrypt.service don't even have a [Install] section and can't be
> enabled at all
'disabling' a
Am 07.09.20 um 10:00 schrieb Ulrich Windl:
>> Anyway, long story short: you typically do not enable services that
>> are only supposed to activated by timer units, enabling those timers
>> should entirely suffice, and the timers will start the services when
>> the time comes.
>
> Interesting:
>>> Lennart Poettering schrieb am 04.09.2020 um 18:36
in
Nachricht <20200904163639.GU267847@gardel-login>:
> On Mo, 31.08.20 16:50, Konstantin Ryabitsev (konstan...@linuxfoundation.org)
> wrote:
>
>> On Mon, Aug 31, 2020 at 04:49:32PM ‑0400, Kevin P. Fleming wrote:
>> > Yes, to get the
