![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2023-03-10 21:59, Dave Howorth wrote:
On Fri, 10 Mar 2023 20:49:45 +0100 "Carlos E. R." <> wrote:
On 2023-03-10 17:01, Per Jessen wrote:
Carlos E. R. wrote:
And anyway, probing messagges are noise by definition, unless there is a "I can not probe at all", and this can be told to the user in the same dialog where I ask to open the scanner or probe for it. The messages about the progress of the probing are not to go into the warning log. [snip] The syslog definition is correct, the problem is the programs defining their debug messages as warnings.
I'm with Per here. There's no way a developer will see any messages on your systems, so either the messages are wrongly classified or configured in the application or they aren't debugging messages.
That's exactly what I am saying! They are wrongly classified or configured in the applications. My normal action when I see a warning message is dispatch a bug, something is wrong. But there are way too many! The criteria for sending a message as "warning" to syslog has become too lax, applications are now way more verbose (as warnings) that they were a decade ago.
Well, seeing as your ideas of debugging are quite different to mine, I guess it is time for a bugzilla or a pull request.
Which I do. I have posted several bugzillas, but it is a lot of work, one per noisy message.
Recently:
Bug 1207778 - systemd complains: Failed to resolve group 'brltty'
I'm impressed :)
An update has been submitted.
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.
I use both.
Why I am not surprised :-)
Me too.
We remove mail.{info,err,notice} on all machines, and I only have one single machine that has any use for news.{crit,err,notice} - our news-server.
I can understand removing news logs if there is no news handling in a machine, but all my machines send email. If there is a problem and the log is disabled, it would be a disaster.
I don't know about your MUA but in mine (Claws) if I have a problem sending a message I go to the menus: Tools/Network Log and have a look at exactly what was sent over the wire. If necessary i restart the program from the command-line and increase logging further. No need to go to any system logs and no problem if they're missing.
Well, there is a difference: my MUAs hand over the email to postfix for sending. This was a necessity long ago, because I used Alpine as MUA. Now it is a preference. And in this machine, I run an nntp (news) proxy server, so there is a lot of writing in the news logs. So much that the systemd journal is swamped, because it doesn't have the capability to filter anything out. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)