From: "Darrick J. Wong" <djwong@kernel.org>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: [PATCH 4/2] debian: don't restart e2scrub_all when upgrading package
Date: Tue, 9 Jan 2024 21:57:24 -0800 [thread overview]
Message-ID: <20240110055724.GC722946@frogsfrogsfrogs> (raw)
In-Reply-To: <170268089742.2679199.16836622895526209331.stgit@frogsfrogsfrogs>
From: Darrick J. Wong <djwong@kernel.org>
When installing or upgrading the e2fsprogs package, only start the
e2scrub_all timer and the reaping service. Don't restart e2scrub_all
itself, because that will kill any scrubs in progress, which will
trigger the failure reporting.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
debian/rules | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/debian/rules b/debian/rules
index b85976f0..0120fe6a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -148,6 +148,10 @@ override_dh_installinfo:
dh_installinfo -pcomerr-dev ${stdbuilddir}/lib/et/com_err.info
dh_installinfo -plibext2fs-dev ${stdbuilddir}/doc/libext2fs.info
+override_dh_installsystemd:
+ dh_installsystemd -p e2fsprogs --no-restart-after-upgrade --no-stop-on-upgrade e2scrub_all.timer e2scrub_reap.service
+ dh_installsystemd --name=service1
+
override_dh_makeshlibs:
for i in $(SYMBOL_LIBS); \
do \
next prev parent reply other threads:[~2024-01-10 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 22:55 [PATCHSET] e2scrub: fix some problems Darrick J. Wong
2023-12-15 22:56 ` [PATCH 1/2] e2scrub: fix pathname escaping across all service definitions Darrick J. Wong
2023-12-15 22:56 ` [PATCH 2/2] e2fsprogs: don't allow udisks to automount ext4 filesystems with no prompt Darrick J. Wong
2023-12-31 20:39 ` [PATCH 3/2] e2scrub_fail: move executable script to /usr/libexec Darrick J. Wong
2023-12-31 21:37 ` Neal Gompa
2024-01-10 5:57 ` Darrick J. Wong [this message]
2024-01-10 5:58 ` [RFC PATCH 6/2] e2scrub: skip filesystems that don't have journals Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240110055724.GC722946@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox