From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common 1/3] systemd: enter scope: allow specifying 'Before' and 'After' properties
Date: Wed, 17 Dec 2025 14:17:10 +0100 [thread overview]
Message-ID: <20251217131724.118681-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20251217131724.118681-1-f.ebner@proxmox.com>
The value is an array reference with a list of unit names.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/Systemd.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/Systemd.pm b/src/PVE/Systemd.pm
index 8fc06a5..6ff0dc8 100644
--- a/src/PVE/Systemd.pm
+++ b/src/PVE/Systemd.pm
@@ -113,7 +113,7 @@ sub enter_systemd_scope {
my $properties = [[PIDs => [dbus_uint32($$)]]];
foreach my $key (keys %extra) {
- if ($key eq 'Slice' || $key eq 'KillMode') {
+ if ($key eq 'Slice' || $key eq 'KillMode' || $key eq 'After' || $key eq 'Before') {
push @{$properties}, [$key, $extra{$key}];
} elsif ($key eq 'SendSIGKILL') {
push @{$properties}, [$key, dbus_boolean($extra{$key})];
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-12-17 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 13:17 [pve-devel] [PATCH-SERIES common/qemu-server 0/3] fix #7092: systemd: vmid.scope: add orderings to fix dbus-vmstate cleanup (regression) Fiona Ebner
2025-12-17 13:17 ` Fiona Ebner [this message]
2025-12-17 13:17 ` [pve-devel] [PATCH qemu-server 2/3] " Fiona Ebner
2025-12-17 13:17 ` [pve-devel] [PATCH qemu-server 3/3] dbus-vmstate: guard more errors in qemu_del_dbus_vmstate() Fiona Ebner
2025-12-17 14:05 ` [pve-devel] [PATCH-SERIES common/qemu-server 0/3] fix #7092: systemd: vmid.scope: add orderings to fix dbus-vmstate cleanup (regression) Maximiliano Sandoval
2025-12-17 14:16 ` [pve-devel] applied-series: " Fabian Grünbichler
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=20251217131724.118681-2-f.ebner@proxmox.com \
--to=f.ebner@proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox