[Letsencrypt-devel] Bug#843607: Bug#843607: systemd timer option RandomizedDelaySec not available on debian jessie

Lorenzo Felice Cameroni lorenzo.cameroni at gmail.com
Wed Nov 9 16:39:42 UTC 2016

You are right, systemd shoud remain optional.
The right options should be
- add a dependancy on upstart OR sysvinit-core OR systemd-sysv >= 229
(as you said this would cause people using systemd to use the
backported version)
- do not use systemd timer on jessie-backport and use cron

A third option can be remove the random delay from certbot.timer and
add it to the certbot.service "ExecStart" property, but I can't help
as I'm not familiar with systemd syntax


Lorenzo Cameroni

2016-11-09 16:50 GMT+01:00 Axel Beckert <abe at debian.org>:
> Hi,
> Lorenzo Felice Cameroni wrote:
>> - add a versioned dependency on certbot to systemd >= 229
> Please do _not_ do that. There are enough people who do not want
> systemd on a server. And pulling in a backport of an init system just
> for getting SSL certificates sounds very disproportionate.
>> - do not use systemd timer on jessie-backport and use cron
> Well, certbot works fine on Sid without systemd either, so there
> should not be much to do to get that. At least /etc/cron.d/certbot
> exists.
> It probably suffices to not install /lib/systemd/system/certbot.timer
> and to remove the "is systemd running" check from /etc/cron.d/certbot.
>                 Regards, Axel
> --
>  ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

More information about the Letsencrypt-devel mailing list