From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] systemd: Silence console output when updating the package.
Date: Sun, 12 Feb 2023 11:14:32 +0100 [thread overview]
Message-ID: <20230212101433.269851-1-stefan.schantl@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
Otherwise there are hints about non executed operations
displayed because systemd does not run or lives in a chrooted
environment.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
systemd/systemd.nm | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/systemd/systemd.nm b/systemd/systemd.nm
index c8e378a38..f1985908b 100644
--- a/systemd/systemd.nm
+++ b/systemd/systemd.nm
@@ -312,7 +312,7 @@ packages
script postup
# Re-exec systemd after update.
- /usr/bin/systemctl daemon-reexec
+ /usr/bin/systemctl daemon-reexec >/dev/null 2>&1 || :
# Restart login service after update
/usr/bin/systemctl daemon-reload >/dev/null 2>&1 || :
@@ -320,12 +320,9 @@ packages
# Use the new journald configuration file and restart the service.
if ! grep -xq ImportKernel=yes /etc/systemd/journald.conf ; then
- mv /etc/systemd/journald.conf.paknew /etc/systemd/journald.conf
+ mv /etc/systemd/journald.conf.paknew /etc/systemd/journald.conf >/dev/null 2>&1 || :
/usr/bin/systemctl restart systemd-journald.service >/dev/null 2>&1 || :
fi
-
- # Enable spawning getty's on serial devices.
- systemctl enable serial-getty(a).service >/dev/null 2>&1 || :
end
# Be sure to start the new udev after everything is done.
--
2.30.2
next reply other threads:[~2023-02-12 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 10:14 Stefan Schantl [this message]
2023-02-12 10:14 ` [PATCH 2/2] systemd: Proper spawn a getty on TTY1 Stefan Schantl
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=20230212101433.269851-1-stefan.schantl@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.org \
/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