From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer] unconfigured.sh: set kernel.printk to level warn
Date: Fri, 24 Jan 2025 13:40:28 +0100 [thread overview]
Message-ID: <f97f923e-7d4b-407c-8ee0-38fe2c3ed52c@proxmox.com> (raw)
In-Reply-To: <20241126184211.988025-1-s.ivanov@proxmox.com>
Am 26.11.24 um 19:42 schrieb Stoiko Ivanov:
> we got a few reports of kernel-output drawing over the TUI-installer.
> (e.g. when ZFS loads for the pool-cleanup, also mkfs.xfs sometimes
> triggers a message being printed).
>
> As the information gets logged in the kernel ringbuffer (`dmesg`)
> anyways, there's little gain on having it displayed on the console in
> addition.
>
> following https://www.kernel.org/doc/Documentation/sysctl/kernel.txt
> and
> https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/getting-started-with-kernel-logging_managing-monitoring-and-updating-the-kernel
> simply set the sysctl to log only messages of level warn and above to
> the console.
>
> Tested in a VM, where I manually ran the command before starting the
> TUI installer (and selecting XFS as filesystem there). without it the
> messages got displayed, with the command they did not.
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> as it's a cosmetic issue I would not pull it in late in the release cycle.
> Sending it nonetheless now, in order not to forget it.
>
> unconfigured.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-24 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 18:42 [pve-devel] " Stoiko Ivanov
2025-01-24 12:40 ` 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=f97f923e-7d4b-407c-8ee0-38fe2c3ed52c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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