On Thursday, 21 May 2020 07:44:24 UTC+10, kobuki wrote: > > I've upgraded my 3.9.3 to 4.0.0 on a Debian 10. Unfortunately logging now > is all over the place. >
Sounds a little harsh. Program name for rsyslog filters is either 'weewx' or 'weewxd' or on a > second weewx instance, 'weewx-name'. > I am running V4 under Debian 10 and see no 'weewxd' in the logs, but then again I only run setup.py installs and not package installs. 'weewx-name' for a second WeeWX instance is (and always has been) expected behaviour; if you are logging to a single file different program names for each WeeWX instance makes debugging far easier, also makes it far easier to log each instance to separate files. But then it ignores 'debug = 0' in weewx.conf when a module uses > syslog.syslog() calls instead of the new Python logger. Modules put out > debug messages in the log. The old "central" debug setting used to take > care of them. Can I set the syslog logging level somehow in config for all > modules that still use the facility? > I doubt whether there will be any magic button you can press in a config file since V4 now uses the python logging module in lieu of the syslog module and consequently the old syslog setup code was removed in V4. There may well be some magic syslog incantation that someone will provide, but I suspect you will be best served by contacting the 3rd party extension authors and asking them to update their extension to work (properly) with V4. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d3f32967-7039-4396-8080-9df83b8a688b%40googlegroups.com.
