Not sure why you are thanking me, you took no notice of what I suggested. Commenting out log lines is a poor choice, in future if you ever want to troubleshoot you have no means of obtaining any meaningful log info unless you again modify source code. A better solution is to change the log level of the noisy log output as i suggested so that it is only logged when you run WeeWX with debug = 1.
Gary On Saturday, 23 January 2021 at 11:37:31 UTC+10 mksm...@gmail.com wrote: > Commenting out line 78 or line 107 only did not work, but Commenting out > (line 78 & 107) did the trick. no more unnecessary writing to (/var/log) > > Thank you *vince & gjr80* > > On Saturday, January 23, 2021 at 3:16:42 AM UTC+3 gjr80 wrote: > >> If it's this one >> <https://gitlab.com/wjcarpenter/bme280wx/-/blob/master/bin/user/bme280wx.py> >> then the only change that is needed is to change the loginf() call at >> line 78 to logdbg(). Everything else should be left untouched. >> Commenting out logging to fix a chatty log is really a case of cutting off >> your nose to spite your face. Just like restarting WeeWX daily, far better >> to engineer out the problem. >> >> Gary >> >> On Saturday, 23 January 2021 at 10:06:06 UTC+10 vince wrote: >> >>> We'd have to see 'exactly' what code you have installed now in order to >>> help. At this point we've seen so many partial descriptions that it's >>> impossible to know what exactly you're currently running and what error >>> messages you are seeing when you run that code. >>> >>> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4548c654-0f8d-42a0-b1fd-9c59604eab1cn%40googlegroups.com.
