I think you need more than just the conditional (weewx.debug>=2) around the stack trace. I played with that and while it works ok, the systemd log will show that weewx exited but then ran a few more loops. In other words its out of order, so a user looking at the log wonders "?what?" It seems to me that weewxd.py ought to set a global exit flag and wait a bit for drivers, engine etc to return and then exit via a simple return statement. I'm not a python person but thats the general gist of my idea.
-- 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/c3e5c07a-3eb8-4a29-a683-ad3ae499aaea%40googlegroups.com.
