I'm using WeeWX on a RPi but there are also many other systems running simultaneously. I'm using a single bash script used by rc.local file and crontab that checks and manages all systems. Implementing WeeWx into my system like that just is a convenient way for me to not 'break' my system architecture and keeping things simple.
So far I did not encounter issues, so I'm happy :) Again Tom, thank you very much for this great project and your efforts! On Saturday, March 2, 2019 at 10:01:45 PM UTC+1, Tom Keffer wrote: > > The init.d scripts files do more than just start weewx. They also make > sure essential services are up and running before attempting the startup. > > So, let me flip the question around: is there any reason *not* to use the > init.d script? Is there something you need to work around that attracts you > to putting the start up in the rc.local file? > > -tk > > > > On Sat, Mar 2, 2019 at 11:40 AM <[email protected] <javascript:>> wrote: > >> On Sunday, February 24, 2019 at 11:42:22 AM UTC-8, Henry Denston wrote: >>> >>> Ok, thanks Tim, good advice! :) >>> >>> So basically there is no need to use the file from >>> util/init.d/weewx.debian like the DOCs advice. >>> So there is no downside by not using the instruction from the >>> documentary and just execute the ./bin/weewxd weewx.conf file with the >>> weewx.conf as first parameter from the /etc/rc.local file? >>> >> >> >> The downside is that if you start/stop weewx via some custom mechanism, >> we will have a difficult time helping you for future questions....and you >> will have a difficult time updating weewx to future versions (maybe). >> >> >> - If you are running a systemd-based operating system, start weewx >> with a systemd-based startup file >> - If you are running an init.d-based operating system, start weewx >> with an init.d-based startup file >> >> >> But 'technically' weewx does not care how you start it up. You can do >> it any way you want. >> >> >> >
