On the Mac, a rotating file handler will be the default starting with
V4.0.1.

3-may-2020 commit 6348741
<https://github.com/weewx/weewx/commit/6348741c64f55c5b2d34d9b9c70a5ed0b6d55c7f>

On Tue, May 19, 2020 at 7:19 PM Chris Alemany <[email protected]> wrote:

> May I please put a hand way up for default file-based logging? This would
> be wonderful for MacOS X.  The log viewed through the standard “Console” in
> MacOS X is chock full and terrible. A dedicated file would make
> troubleshooting so much cleaner. (/var/log is a common spot in MacOS X but
> weewx also installs in its own space so people the log there would be nice
> too). I realize it’s not a voting thing… just my 2cs from the apple shaped
> seats. :)
>
> On May 19, 2020, at 6:14 PM, mwall <[email protected]> wrote:
>
>
>
> On Tuesday, May 19, 2020 at 9:00:18 PM UTC-4, Tom Mitchell wrote:
>>
>> FWIW, I have been using phusion/baseimage
>> <https://phusion.github.io/baseimage-docker/> as a base for my Docker
>> builds and it pipes syslog to stdout by default - that works fine for me.
>>
>> That said, I think it would be better if weewx were to log to stdout by
>> default since it is kind of the default for Unix/variants. Not depending on
>> syslogd seems like a nice simplification of the runtime.
>>
>
>
> it is probably incorrect for weewx to assume that syslog exists, but not
> because it is not the 'unix way'.  on the contrary, syslog IS the unix
> way.  systemd is perverting the 'unix way', and not in a helpful or good
> way.
>
> it is quite helpful to have weewx log messages in syslog - if there are
> hardware issues, or clock skew, or usb devices plugging/unplugging, or
> other system stuff happening, you see it right there with the weewx
> messages.  makes diagnostics much easier.
>
> we had to make a syslog shim to do the windows port of weewx, so not
> depending on syslog has other benefits too.
>
> emitting log messages to stdout is not appropriate, and is definitely not
> the 'unix way'.  log messages should go to the log, whether that is syslog,
> syslog-redirected-to-rsyslog-server, a file in /var/log, or whatever.
>
> when you run weewx directly, the observation data go to stdout.
>
> it would be more appropriate to default the log output to a file, with log
> rotation (preferably date-time stamped names, not incrementing index
> names).  for example, for a setup.py install the log would go to
> /home/weewx/log/weewx and for a deb/rpm install the log would go to
> /var/log/weewx
>
> of course, it must be easy to change the name of the basename of the log
> file so that multiple instances of weewx can send to different files, each
> with their own rollovers
>
> 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/3aea5121-69a6-436c-8ddf-f51636142de6%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-development/3aea5121-69a6-436c-8ddf-f51636142de6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
> --
> 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/018C9240-38A2-4619-A96A-8E55C4C60CE0%40gmail.com
> <https://groups.google.com/d/msgid/weewx-development/018C9240-38A2-4619-A96A-8E55C4C60CE0%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAPq0zECwQynr_O2Kj5OBTqSXQaHA7AjNgZq_Nqij7WZ5EmqMig%40mail.gmail.com.

Reply via email to