Re: [weewx-development] Re: V5.0.0b17 available

[Joel Bion]

Here’s a thought: Why not write a short bash or Python script that looks to see where weewx is logging and when finding it either: 1) prints out help text telling the user where to find it Or 2) starts dumping the log to stdout.  And on error, reports “can’t find it” Is this reasonable? Or are the places so varied and undeterminable at runtime that such a script would be unwritable? Joel On Dec 15, 2023, at 9:27 AM, Vince Skahan <vinceska...@gmail.com> wrote:  5.0b17 looks like it takes a fine approach already to me. systemd systems can always use journalctl to read the logs.  Add the '-u weewx' flag to see just weewx entries. if you 'also' have rsyslogd installed and enabled, you can 'also' use /var/log/weewx/weewx.log to view the same entries as of 5.0b17 if you do 'not' have rsyslogd installed+enabled it's no harm that weewx drops config files into place for rsyslogd.  They are tiny and wound not be used. So it looks perfect to me.  Other than systemd.  I am not on 'team systemd' to say the least although I have to accept that borg won :-) Users of any and all systemd-laden operating systems just have to accept that if they see references to /var/log/syslog or /var/log/messages that 'in general' they need to either use journalctl to view logs 'the systemd way', or they alternately need to 'add' rsyslogd to use legacy logging that has worked for over 40 years before the systemd borg attacked and won. FWIW - the official debian12 vagrant box has rsyslog installed, configured, and running with a very normal looking rsyslog.conf, so that's already done for that setup.  logrotate is also present and normally configured with typical entries under /etc/rsyslog.d If you do official debian12 under 'docker' you get a very minimal setup where neither logrotate nor rsyslogd are installed.  Neither make a lot of sense in docker anyway, but in any event if weewx writes config files for things that don't exist in the os, it's tiny and benign at worst. -- 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 weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/a2e034c1-22a0-4009-9575-1831506db96fn%40googlegroups.com. -- 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 weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/DAE8BFCE-785C-4759-9405-5956DA02D9DA%40gmail.com.