From: Friedrich Weber <f.weber@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Mira Limbeck <m.limbeck@proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 7/7] report: add recent boot timestamps which may show fencing/crash events
Date: Thu, 17 Oct 2024 14:02:08 +0200 [thread overview]
Message-ID: <102ce1fb-383d-4391-9c2a-c33f9fdecd40@proxmox.com> (raw)
In-Reply-To: <d205f7db-51fe-4afd-b0cb-5e94d344b07c@proxmox.com>
I think having recent boot timestamps and kernel versions in the report
would be nice, I can think of some situations where having this info
available upfront would have sped things up.
I just checked, the patch still applies cleanly.
On 19/04/2024 10:56, Mira Limbeck wrote:
> [...]
> The kernel command line makes sense up there. I agree.
> But the reboots are often less interesting/important than the pveversion
> output.
> So I'd prefer the pveversion output to stay as far up as possible (after
> hostname, date and cmdline).
Regarding the placement of the `last` output, I agree with Mira though
-- I'd also prefer to keep pveversion as far up as possible.
_______________________________________________
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:[~2024-10-17 12:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 9:16 [pve-devel] [PATCH manager 1/7] report: add kernel command line from current boot Alexander Zeidler
2024-04-18 9:16 ` [pve-devel] [PATCH manager 2/7] report: create "jobs" section, add `jobs.cfg` Alexander Zeidler
2024-04-18 20:25 ` [pve-devel] applied: " Thomas Lamprecht
2024-04-18 9:16 ` [pve-devel] [PATCH manager 3/7] report: add `apt-cache policy` to list recognized APT sources Alexander Zeidler
2024-04-18 20:28 ` [pve-devel] applied: " Thomas Lamprecht
2024-04-18 9:16 ` [pve-devel] [PATCH manager 4/7] report: list held back packages Alexander Zeidler
2024-04-18 20:28 ` [pve-devel] applied: " Thomas Lamprecht
2024-04-18 9:16 ` [pve-devel] [PATCH manager 5/7] report: overhaul `dmidecode` related output Alexander Zeidler
2024-04-18 10:24 ` Mira Limbeck
2024-04-18 12:30 ` Alexander Zeidler
2024-04-18 9:16 ` [pve-devel] [PATCH manager 6/7] report: add info about (un)used memory slots Alexander Zeidler
2024-04-18 10:16 ` Aaron Lauterer
2024-04-18 13:32 ` Alexander Zeidler
2024-04-18 10:20 ` Mira Limbeck
2024-04-18 13:38 ` Alexander Zeidler
2024-04-18 9:16 ` [pve-devel] [PATCH manager 7/7] report: add recent boot timestamps which may show fencing/crash events Alexander Zeidler
2024-04-18 10:43 ` Mira Limbeck
2024-04-18 15:45 ` Alexander Zeidler
2024-04-19 8:56 ` Mira Limbeck
2024-10-17 12:02 ` Friedrich Weber [this message]
2024-04-18 9:19 ` [pve-devel] [PATCH manager 1/7] report: add kernel command line from current boot Alexander Zeidler
2024-04-18 10:16 ` Aaron Lauterer
2024-04-18 11:05 ` Mira Limbeck
2024-04-18 15:46 ` Alexander Zeidler
2024-04-18 20:25 ` [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=102ce1fb-383d-4391-9c2a-c33f9fdecd40@proxmox.com \
--to=f.weber@proxmox.com \
--cc=a.zeidler@proxmox.com \
--cc=m.limbeck@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