From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH corosync-pve] start corosync.service after syslog
Date: Tue, 15 Sep 2020 10:36:42 +0200 [thread overview]
Message-ID: <20200915083642.968437-1-aderumier@odiso.com> (raw)
Currently we don't have any log at shutdown
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
---
...-start-corosync.service-after-syslog.patch | 25 +++++++++++++++++++
debian/patches/series | 1 +
2 files changed, 26 insertions(+)
create mode 100644 debian/patches/0003-start-corosync.service-after-syslog.patch
diff --git a/debian/patches/0003-start-corosync.service-after-syslog.patch b/debian/patches/0003-start-corosync.service-after-syslog.patch
new file mode 100644
index 0000000..eb44346
--- /dev/null
+++ b/debian/patches/0003-start-corosync.service-after-syslog.patch
@@ -0,0 +1,25 @@
+From 673fbb667b5ab85089b6a977322109ef13a8b43c Mon Sep 17 00:00:00 2001
+From: Alexandre Derumier <aderumier@odiso.com>
+Date: Tue, 15 Sep 2020 10:31:33 +0200
+Subject: [PATCH] start corosync.service after syslog
+
+Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
+---
+ init/corosync.service.in | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/init/corosync.service.in b/init/corosync.service.in
+index adf7080..f0aefbe 100644
+--- a/init/corosync.service.in
++++ b/init/corosync.service.in
+@@ -5,6 +5,7 @@ ConditionKernelCommandLine=!nocluster
+ ConditionPathExists=/etc/corosync/corosync.conf
+ Requires=network-online.target
+ After=network-online.target
++After=syslog.service
+
+ [Service]
+ EnvironmentFile=-@INITCONFIGDIR@/corosync
+--
+2.20.1
+
diff --git a/debian/patches/series b/debian/patches/series
index fd3a2f0..1b4a4c9 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
0001-Enable-PrivateTmp-in-the-systemd-service-files.patch
0002-only-start-corosync.service-if-conf-exists.patch
+0003-start-corosync.service-after-syslog.patch
--
2.20.1
reply other threads:[~2020-09-15 8:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200915083642.968437-1-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.