On Friday, December 15, 2023 at 9:25:40 AM UTC-5 [email protected] wrote:


Maybe a caveat  is needed that WeeWx V5 will try to create a dedicated log 
file, but may not under some OS.
Currently under the WeeWx Debian set up  Verify section there is this 
check the log file:
tail -50 /var/log/weewx/weewx.log
Rather than be helpful this will trigger confusion when the command fails 
because .var/log/weewx/weewx.log does not exist.


thank you paul!

we might have to remove all the log-related recipes from the docs and refer 
to wiki pages instead; one cannot create timeless docs when the os removes 
tried-and-true methods for interacting with the system.

we had to create a wiki page exactly for this reason:

https://github.com/weewx/weewx/wiki/view-logs

the logrotate and rsyslog conf files are *supposed* to be conditional for 
the pip installs.  does this mean that a "pure systemd-journald" debian 
still has a directory /etc/rsyslog.d?  existence of that directory is what 
we use to determine whether to deploy the syslog and logrotate confs.

we will probably have to move them to the postinst for debian packages 
(along with the init stuff, since not every system uses systemd).  that 
would be a hassle, since doing things in post removes all of the file 
comparisons and version-checking that come with debian packaging.

we considered using python's logging system exclusively, that way we avoid 
the systemd-journald borgification of logging.  but python's logging has 
other issues, most notably that it cannot ensure a consistent log when 
multiple processes try to write to the same file.

on the other hand, we might be safer to just deploy them anyway, because 
anyone serious about logging will install syslog.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" 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-development/47679f66-1c7a-428d-b3ba-b60c62c54b33n%40googlegroups.com.

Reply via email to