all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Reiter <s.reiter@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH 0/2] Work around systemd warning about KillMode 'none'
Date: Mon, 21 Jun 2021 18:35:40 +0200	[thread overview]
Message-ID: <20210621163542.1752647-1-s.reiter@proxmox.com> (raw)

systemd deprecated KillMode 'none', but we still need it, since we manage our VM
scopes/slices manually via another service, 'pve-guests.service'. To this
extent, replicate the previous behaviour without using the deprecated mode.

Example log message:
/run/systemd/transient/101.scope:3: Unit configured to use KillMode=none. [...]

I still get the same warning about a 'ceph-volume@.service' in my logs, after
upgrading to pacific, though I'm not sure if that's something we need to/can
fix, or something left over from the upgrade - any ceph expertise welcome :)


qemu-server: Stefan Reiter (1):
  use KillMode 'process' for systemd scope

 PVE/QemuServer.pm | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

common: Stefan Reiter (1):
  systemd: allow SendSIGKILL and TimeoutStopUSec dbus properties

 src/PVE/Systemd.pm | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
2.30.2




             reply	other threads:[~2021-06-21 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 16:35 Stefan Reiter [this message]
2021-06-21 16:35 ` [pve-devel] [PATCH qemu-server 1/2] use KillMode 'process' for systemd scope Stefan Reiter
2021-06-22  6:02   ` Thomas Lamprecht
2021-06-22  7:23     ` Stefan Reiter
2021-06-23 10:06   ` [pve-devel] applied: " Thomas Lamprecht
2021-06-21 16:35 ` [pve-devel] [PATCH common 2/2] systemd: allow SendSIGKILL and TimeoutStopUSec dbus properties Stefan Reiter
2021-06-22  5:45   ` [pve-devel] applied: " Thomas Lamprecht

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=20210621163542.1752647-1-s.reiter@proxmox.com \
    --to=s.reiter@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal