On 01.08.23 21:08, AlMa wrote:
This is a rather naive understanding of how logging is done in practice. The reality is that developers often don't know (and maybe can't know) just how severe an odd condition may be in practice.Unfortunately, neither do I. Though seemingly unrelated journal-visible issues are quite often indeed independent, sometimes unexpected interactions or common root causes occur.
Perhaps, there should be a category for tentative errors and/or tentative warnings (i.e., with an unknown (or yet unknown) severity in practice). E.g., dereferencing a zero pointer, or division by zero, or garbled screen output, or the inability to read '/' as the root user, etc. are almost always errors (except when you test error-handling routes themselves; then a division by zero is not a bug but a must). If you say that it is unknown how severe a message such as “ACPI Warning: SystemIO range … conflicts with OpRegion … . lpc_ich: Resource conflict(s) found affecting gpio_ich” really is, it should not be a warning (especially, it should not warn the reader) but be a tentative warning (i.e., it might warn the reader in the future or under particular circumstances). The (new?) colors of the tentative errors and warnings should be clearly stated in the manpages of journalctl.