From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 05D2E3858D35 for ; Tue, 16 Apr 2024 10:56:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 05D2E3858D35 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 05D2E3858D35 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713264988; cv=none; b=rsRyfd2mHAARodrzSLep7N6oaZNtpGX1MG0zxYPV1OdTjhUAit/p+NqGHT4vyZAj3I6vbCUoSzadoI6SBdzGntml9kRWUeTVNc/B7GGGT28qum2jT2i2AatDbucDXFAg2pt9WsDr/Vph0eaNCR4XgnQVmaZMJdTgl8ISOOCMRPo= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713264988; c=relaxed/simple; bh=AfIVm7OPwdGu3TUT5QrRzMXYZCw4xH3GCsipkJJh5W8=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=Kidu4o0TDeY6J0XU2OQdHS/tKGoFpsJJf3KnuG3/KH1gaYzyHrdnoNkjoa8F0fxHm6eDd/Ehw2UpP66dpbW51HIjXVRPq4brgwnO38+GSiWBFYJq6j9TGX1/CaQRwI8/B5XtYc/qvzw2Z4GMHxE3DukVrRD8vFqQllrkTg+FzmE= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1713264986; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=vn9MPQIOEMMOM5JMwGEQM15cMRpHuhN0vmStNIZwDD4=; b=UKU0R745yTrJgMESS0VoqzRBLO3btq9ricyv0Ay+lHhDFZct0/OfgmcynNsvUAPIT/4VJu SGY+YFXTWn2XztPZeib6Vks+yhgCL7fRArn2bJ3lg6IRe7GdX4VO9AW4jWPRoMrYFoK29M J37xtGa28yDGfRXptGhelHr8zCah9uc= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-519-Uk8xMcytOKyuOPijrwKmrg-1; Tue, 16 Apr 2024 06:56:23 -0400 X-MC-Unique: Uk8xMcytOKyuOPijrwKmrg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2081F29AB403; Tue, 16 Apr 2024 10:56:23 +0000 (UTC) Received: from redhat.com (unknown [10.22.8.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1017040B497A; Tue, 16 Apr 2024 10:56:23 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1rwgUA-0001Z2-2u; Tue, 16 Apr 2024 06:56:22 -0400 Date: Tue, 16 Apr 2024 06:56:22 -0400 From: "Frank Ch. Eigler" To: brobecker@adacore.com Cc: gdb@sourceware.org, gcc@gcc.gnu.org Subject: adacore git-hooks - daemon-mode email vs. systemd-logind linger Message-ID: <20240416105622.GD1423@redhat.com> MIME-Version: 1.0 User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-7.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,PDS_BRAND_SUBJ_NAKED_TO,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi, Joel - As a part of more security review on sourceware, I had recently experimented with systemd logind's KillUserProcesses=yes option. It turns out that this nuked one aspect adacore hooks' post-receive processing, which create a background process to slowly dribble out emails. I restored KilledUserProcesses=no for now, but I'd really like to set that back. That means the hooks would have to change. Here are a couple of options: - just send the emails immediately, without the daemon stuff; if the delays are there to try to sequentialize them, consider instead getting the hooks to emit Message-Id:/In-Reply-To:/Date: headers to let MUA's sort properly at reception - invoke the email sending wrapped in a "systemd-run --user" deferred execution gadget, including a "sleep XXX" if you must keep time-hope-based sequencing - move email stuff entirely out of the hooks; these repos are "public property" anyhow, and we can put cron jobs in place elsewhere to trigger email notifications about commits; heck, they could run the hook code itself later, just feed it retrospective git-hook lines - FChE