From: Gabriel Goller <g.goller@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox{, -backup} 0/3] Always print workertask start and end logs to syslog
Date: Wed, 3 Sep 2025 16:13:44 +0200 [thread overview]
Message-ID: <20250903141349.268228-1-g.goller@proxmox.com> (raw)
This series adds a few things:
* print a workertask start message to the syslog and the tasklog
* always print the result message to the syslog
* add the upid to the task's start and end messages
This allows us to see which tasks have been started and when regardless of the
tracing filtering and task result status.
proxmox:
Gabriel Goller (2):
worker_task: always print the result message to the syslog
worker_task: print worker starting message and upid
proxmox-rest-server/src/worker_task.rs | 32 ++++++++++++++++++++------
1 file changed, 25 insertions(+), 7 deletions(-)
proxmox-backup:
Gabriel Goller (1):
prune: add upid to workertask log_result function
src/api2/admin/datastore.rs | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Summary over all repositories:
2 files changed, 28 insertions(+), 8 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-09-03 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 14:13 Gabriel Goller [this message]
2025-09-03 14:13 ` [pbs-devel] [PATCH proxmox 1/2] worker_task: always print the result message to the syslog Gabriel Goller
2025-09-03 14:13 ` [pbs-devel] [PATCH proxmox 2/2] worker_task: print worker starting message and upid Gabriel Goller
2025-09-03 14:13 ` [pbs-devel] [PATCH proxmox-backup 1/1] prune: add upid to workertask log_result function Gabriel Goller
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=20250903141349.268228-1-g.goller@proxmox.com \
--to=g.goller@proxmox.com \
--cc=pbs-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.