On Thursday, March 23, 2017 at 10:56:40 AM UTC-4, bgrattan wrote: > > Susan's comment below seems to make sense that things that weewx needs > aren't starting fast enough. Is there a way to initiate the restart but > delay it to wait for what it needs? >
bob, there are at least two strategies for dealing with unavailable resources: 1) configure your init system to deal with it. in this case, you would modify the init system's configuration files to let it know that weewx should not be started until after the resource(s) are available. for an rc/upstart system that would be /etc/init.d/weewx, for a systemd system that would be /etc/systemd/system/weewx.service. 2) configure weewx to deal with it. use the loop_on_init=true in weewx.conf to tell weewx that it should keep retrying during startup (normal behavior is to quit on startup when required resources are not available). however, we should be sure that there is not a conflict between the way weewx daemonizes itself and the way systemd tries to assimilate^H^H^H^H^H^H^H^H^H^H manage weewx. (sorry, the scars are still tender from fighting systemd on a cluster node with 24-cores and 10TB of disk) m -- 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]. For more options, visit https://groups.google.com/d/optout.
