You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, when we enable LKRG's heartbeat, those messages are getting to the kernel's ring buffer and are seen in dmesg, quickly scrolling other messages out of convenient reach. (Further, on some distros they'd appear on console by default, but we could easily avoid that by lowering their syslog priority. This was also part of the reason why we're not relying on console messages for sending them to the remote, instead reading from the kernel's ring buffer.)
We could want to introduce a type of heartbeat messages that would only be sent over network (when enabled), without flooding dmesg.
The text was updated successfully, but these errors were encountered:
Nov 10, 2022
Right now, when we enable LKRG's
heartbeat
, those messages are getting to the kernel's ring buffer and are seen indmesg
, quickly scrolling other messages out of convenient reach. (Further, on some distros they'd appear on console by default, but we could easily avoid that by lowering their syslog priority. This was also part of the reason why we're not relying on console messages for sending them to the remote, instead reading from the kernel's ring buffer.)We could want to introduce a type of heartbeat messages that would only be sent over network (when enabled), without flooding
dmesg
.The text was updated successfully, but these errors were encountered: