Hello Petr,
On Mon, Dec 08, 2025 at 03:52:37PM +0100, Petr Mladek wrote:
On Fri 2025-12-05 02:21:08, Breno Leitao wrote:
JFYI, I am going to review the last version of the per-console loglevel patchset later this week. IMHO, we are very close to get it merged.
BTW: How often do you ping the netconsole, please? IMHO, adding a short message once-per-hour might be bearable, once-per-minute might be questionable for the kernel buffer but still fine for journalctl.
It is not very often today, about once a week. This is mostly due to the pollution of kernel buffers.
Ideally we can set it to multiple times a day, but less than hourly.
- send messages only to netconsole (this patchset)
I do not have strong opinion about this.
That said, the location /sys/kernel/config/netconsole/<target>/send_msg looks a bit weird to me. I would rather expect /dev/netconsole_msg or so. But I do not have strong opinion. It might be an overkill.
How important is it to trigger the ping from userspace, please? It might be sent by an existing watchdog.
Medium importance, I would say. I am inclined to distributed design, where each machine detects broken netconsole and report itself. Instead of something else (a service) finding broken-netconsole hosts in the "fleet".
Something as:
1. Machine boots 2. userspace sends the ping (or knows that the ping was already sent) 3. the configuration management (chef, ansible, etc) makes sure that the message got received.
So, step number 3 needs to be executed only after step 2. Initiating the ping (step 2) from userspace is the easiest way, to control when the machine can go to step 3.
Thanks --breno