From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1em4gp-0004Gt-6s for guix-patches@gnu.org; Wed, 14 Feb 2018 16:34:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1em4gk-0006lP-AZ for guix-patches@gnu.org; Wed, 14 Feb 2018 16:34:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:35433) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1em4gk-0006lF-6w for guix-patches@gnu.org; Wed, 14 Feb 2018 16:34:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1em4gj-0001rP-Ut for guix-patches@gnu.org; Wed, 14 Feb 2018 16:34:01 -0500 Subject: [bug#30459] Certbot service patches Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55899) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1em4gB-0003xF-Qv for guix-patches@gnu.org; Wed, 14 Feb 2018 16:33:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1em4g8-0006JF-Nz for guix-patches@gnu.org; Wed, 14 Feb 2018 16:33:27 -0500 Received: from mail.lassieur.org ([83.152.10.219]:52646) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1em4g8-0006Dv-8L for guix-patches@gnu.org; Wed, 14 Feb 2018 16:33:24 -0500 From: =?UTF-8?Q?Cl=C3=A9ment?= Lassieur Date: Wed, 14 Feb 2018 22:33:19 +0100 Message-ID: <87y3jv6yu8.fsf@lassieur.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 30459@debbugs.gnu.org Cc: Andy Wingo Hi, Here are a few patches that aim to improve the Certbot service. One problem I have is that reconfiguring takes a bit too much time if there are many certificates. I wonder if there is a way to avoid running 'certbot-activation' when the configuration didn't change. Also, I had not reproducible networking issues while updating the certificates, but they may be related to my deploy hooks and have nothing to do with the service. Comments welcome :-) Clément