public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: PVE development discussion <pve-devel@pve.proxmox.com>,
	Stefan Reiter <s.reiter@proxmox.com>
Subject: [pve-devel] applied: [RFC pve-qemu] Add systemd journal logging patch
Date: Tue, 8 Sep 2020 17:23:49 +0200	[thread overview]
Message-ID: <edf5e764-8249-94b6-0f2d-3d9aa2eeccf9@proxmox.com> (raw)
In-Reply-To: <20200630120620.20176-1-s.reiter@proxmox.com>

On 30.06.20 14:06, Stefan Reiter wrote:
> Prints QEMU errors that occur *after* the "-daemonize" fork to the
> systemd journal, instead of pushing them into /dev/null like before.
> 
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> ---
> 
> Useful for debugging rust panics for example. I'm sure there's other ways to go
> about this (log files? pass the journal fd from outside? pipe it into the
> journal somehow?) but this one seems simple enough, though it of course requires
> linking QEMU against libsystemd.
> 
> @dietmar: is this similar to what you had in mind?
> 
>  debian/control                                |  1 +
>  ...ct-stderr-to-journal-when-daemonized.patch | 50 +++++++++++++++++++
>  debian/patches/series                         |  1 +
>  3 files changed, 52 insertions(+)
>  create mode 100644 debian/patches/pve/0052-PVE-redirect-stderr-to-journal-when-daemonized.patch
> 
>

applied, thanks!




      parent reply	other threads:[~2020-09-08 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200630120620.20176-1-s.reiter@proxmox.com>
2020-09-03 16:30 ` [pve-devel] " Thomas Lamprecht
2020-09-08 15:23 ` Thomas Lamprecht [this message]

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=edf5e764-8249-94b6-0f2d-3d9aa2eeccf9@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@pve.proxmox.com \
    --cc=s.reiter@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal