On 2023-03-10 13:32, Per Jessen wrote:
Carlos E. R. wrote:
For example:
Well, try to look at it from the pov of xsane. xsane has been asked to "look" at your printer, but is unable as the model data is not available. For xsane, that is a problem, albeit not a serious one. Hence a warning.
Asked by whom? Not by me.
Who started up xsane?
I did not tell it to search for that printer.
xsane is probing hardwware (the printer is in the LAN). The messages caused by probing are noise. The warn log should only have serious things.
It seems to me that the nature of a warning is "be careful about this, otherwise something serious might happen".
Nothing serious about it. It is probing for scanners, HP makes scanners, but that one doesn't have a scanner. Noise.
I presume you are actively monitoring /var/log/warn, so that filtering would be much easier to do with a grep.
Of course I do monitor warn, and others. If only warning entries were written to warn, there would be nothing for days. When something appears, it is serious.
I honestly don't know that there is much "of course" about monitoring /var/log/warn. I certain never have - removing it is one of the first customisations we do to any newly installed system.
You remove the file? I'm truly astonished.
To answer $SUBJ - they are not debug messages, they are reports of operational issues.
IMO, they are debug messages. Not important enough to be there. They would be fine in the /var/log/messages. Those softwares run perfectly fine despite the logs. Only something that crashes should go to warn.
To each his own. Anyway, instead of ranting, why don't you put on your admin hat and go reconfigure your syslog not to log warn messages to /var/log/warn ?
Attached is a patch.
I do want warnings. *True* warnings, not noise. Sometimes, I report noise to bugzilla... -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)