From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 334B51FF168 for ; Tue, 26 Nov 2024 19:43:06 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 320B59711; Tue, 26 Nov 2024 19:43:04 +0100 (CET) From: Stoiko Ivanov To: pve-devel@lists.proxmox.com Date: Tue, 26 Nov 2024 19:42:11 +0100 Message-Id: <20241126184211.988025-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.071 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [unconfigured.sh] Subject: [pve-devel] [PATCH installer] unconfigured.sh: set kernel.printk to level warn X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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 --- 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(+) diff --git a/unconfigured.sh b/unconfigured.sh index 070cf33..ef9aa3c 100755 --- a/unconfigured.sh +++ b/unconfigured.sh @@ -233,6 +233,9 @@ chronyd || echo "starting chrony failed ($?)" echo "Starting a root shell on tty3." setsid /sbin/agetty -a root --noclear tty3 & +echo "Setting console loglevel to warn." +sysctl -w kernel.printk='4 4 1 7' + /usr/bin/proxmox-low-level-installer dump-env if [ $proxtui -ne 0 ]; then -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel