From: Stefan Sterz <s.sterz@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Lukas Wagner <l.wagner@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] pvereport: add `date -R` to general system info section
Date: Thu, 23 Feb 2023 16:54:17 +0100 [thread overview]
Message-ID: <34c0fd56-6380-4002-6aa8-322b4717feba@proxmox.com> (raw)
In-Reply-To: <20230223152559.563428-1-l.wagner@proxmox.com>
On 2/23/23 16:25, Lukas Wagner wrote:
> Sometimes it can be quite useful to know when exactly a system report
> was generated. Adds the following output quite prominently in the
> general system info section:
>
While I agree that this can be useful sometimes, just as a heads-up,
iptables-save provides that info already:
# Generated by iptables-save v1.8.7 on Thu Feb 23 16:43:26 2023
However, we may not want to rely on that.
> # date -R
> Thu, 23 Feb 2023 16:21:12 +0100
>
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
> PVE/Report.pm | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/PVE/Report.pm b/PVE/Report.pm
> index d363c15b..c9109dca 100644
> --- a/PVE/Report.pm
> +++ b/PVE/Report.pm
> @@ -29,6 +29,7 @@ my $init_report_cmds = sub {
> order => 10,
> cmds => [
> 'hostname',
> + 'date -R',
> 'pveversion --verbose',
> 'cat /etc/hosts',
> 'pvesubscription get',
next prev parent reply other threads:[~2023-02-23 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 15:25 Lukas Wagner
2023-02-23 15:54 ` Stefan Sterz [this message]
2023-02-23 16:00 ` Lukas Wagner
2023-03-27 13:16 ` Lukas Wagner
2023-03-27 13:30 ` [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=34c0fd56-6380-4002-6aa8-322b4717feba@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=l.wagner@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