Carlos E. R. wrote:
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.
a) you installed xsane b) you accepted the default config c) you started xsane.
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.
If you're keen on only "serious" things being written to /var/log/warn, see my patch.
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?
We remove the logging to it, yes. Nobody ever looks at it. I think it is an ancient relic from early UNIX days. The syslog config has a lot of old crud - for instance: /var/log/mail.info/err/notice /var/log/news/news.crit/err/notice.
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.
Noise is in the eyes (well, ears) of the beholder. -- Wednesday last week, radio SRF1 spent an entire afternoon celebrating the 50th anniversary of the release of "Dark Side of the Moon". I guess that might be noise to some philis .... people.