From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id B3DA56DE0C1B for ; Mon, 15 May 2017 01:30:48 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.495 X-Spam-Level: X-Spam-Status: No, score=0.495 tagged_above=-999 required=5 tests=[AWL=-0.157, SPF_NEUTRAL=0.652] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QpPeQ5Skzu1j for ; Mon, 15 May 2017 01:30:47 -0700 (PDT) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by arlo.cworth.org (Postfix) with ESMTP id 563006DE0BF6 for ; Mon, 15 May 2017 01:30:47 -0700 (PDT) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id ED181100090; Mon, 15 May 2017 11:30:02 +0300 (EEST) From: Tomi Ollila To: Justus Winter , David Bremner Cc: notmuch@notmuchmail.org, notmuch@freelists.org Subject: Re: [Bug] lingering gpg-agents from test suite In-Reply-To: <871srqpns0.fsf@europa.jade-hamburg.de> References: <8737c7zfmp.fsf@tethera.net> <871srqpns0.fsf@europa.jade-hamburg.de> User-Agent: Notmuch/0.24+52~g1f96813 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2017 08:30:48 -0000 On Mon, May 15 2017, Justus Winter wrote: > David Bremner writes: > >> Thanks to changes in gnupg 2.1.20, the agent started by the notmuch test >> suite is no longer killed by deleting the home directory. >> >> So yay, we get to adapt to changes in gnupg, again. >> >> See also >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862093 > > where you write: >> As of 2.1.20, removing $GNUPGHOME is no longer enough for gpg-agent to >> shut itself down. It seems that removing the directory >> /run/user/gnupg/d.$hash is enough to trigger the shutdown. >> >> I'm not sure the underlying cause; perhaps the change to use /run/user >> for non-standard homedirs (which I generally think is sensible) has >> this as a side-effect. > > What triggers the automatic shutdown is the removal of the socket. > 2.1.20 creates the so-called socket directory automatically (if it finds > /**/run/user). > >> The main practical difficulty for me is that this makes it harder for >> test suites using gnupg to work across multiple gpg versions and >> multiple environments. I suppose I'll have to see how far back >> "gpgconf --kill all" is supported. > > Yes, please try to do 'gpgconf --kill all' and ignore the exit status. Quick & dirty: trap 'if command -v gpgconf >/dev/null; then gpgconf --kill all || : fi trap - 0' 0 INT HUP TERM QUIT I'll look a bit more a bit later... Tomi > > > Justus > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch