Tom Keffer <[email protected]> writes: > If all you are seeing is log level ERROR and CRITICAL, then the log level > is too restrictive. I know nothing about FreeBSD, so you're going to have > to figure that out on your own. One thing you could do is have weewx log to > a file. See the wiki > <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#logging-to-rotating-files> > for how to do that.
I've been running weewx on NetBSD since the very end of 2017. FWIW: I am using a USB/serial adaptor and a Davis VP2 serial logger. I am now using a RPI3 (without RTC) and my boot scripts wait for NTP sync before weewx is started. The RPI3 is on a UPS. With this setup, I have very little trouble. It is totally normal on *BSD to use syslog, but syslog config out of the box limits to INFO. So if the OP is not used to configuring syslog (putting weewx into its own log file, allowing debug), files is a good approach. -- 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 visit https://groups.google.com/d/msgid/weewx-user/rmicy1d2nh6.fsf%40s1.lexort.com.
