I can’t figure out why you care about this. It does reveal what was happening
on the thread when WeeWX was shut down. While usually not interesting,
sometimes it might be useful.
> On May 9, 2020, at 10:36 AM, Bill Richter <bill.gotc...@gmail.com> wrote:
>
>
> I agree, that it's ugly. A normal shutdown should not have a stacktrace.
> But wouldn't a simple fix be:
>
> except Terminate:
> log.info("Terminating weewx version %s", weewx.__version__)
> if weewx.debug >= 2:
> weeutil.logger.log_traceback(log.info, " **** ")
> signal.signal(signal.SIGTERM, signal.SIG_DFL)
> os.kill(0, signal.SIGTERM)
>
> I didn't know that the config debug option had more choices that just 1. I
> didn't see that ability defined in the V4 documentation. The user guide
> merely says debug = 1. I'm guessing that it could be debug = 0|1|2... I
> moved from FreeBSD to Raspbian cause of logging support in V4. I want to use
> the application not learn it's internals.
> --
> 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/b11c4670-f8e8-4bd6-aac4-17be3110f267%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/A9C10459-7788-4383-91B6-8C7E0BB066A8%40johnkline.com.
