KILL is definitely not desirable. i'm debugging this now on centos with systemd, weewx, and rtl_433.
for example, the sdr driver spawns the rtl_433 command, and if you kill weewx, you end up with a rogue process, and the next time you start weewx, weewx will fail. as another example, if you are doing database activities, sending a kill could end up in lost data, not because of database transaction atomicity (databases take care of that), but because there can be data in weewx that is not yet inserted. as another example, sometimes it takes weewx awhile to generate a report. so the 60-second default of systemd is not appropriate. we probably should default to a 5 minute default (assuming that no one will have a system where the report generation takes longer than an archive interval, at least not intentionally). -- You received this message because you are subscribed to the Google Groups "weewx-user" 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-user/53c6f4a9-d84e-4526-81a6-4a1dd04bfb45n%40googlegroups.com.
