Yep, either way works. Using screen is like a poor mans service, so to
speak. I use it in that way for other things too. I was using WeewWX with
an SDR (software defined radio) with an acurite for a while and it would
only work that way.
On Sunday, February 24, 2019 at 1:42:22 PM UTC-6,
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
One pro to doing it this way is you can watch the LOOP data as it is coming
in. A good way to debug if nothing else.
On Sunday, February 24, 2019 at 1:28:33 PM UTC-6, Tim Urberg wrote:
>
> One you could use screen, which allows a totally separate screen to be
> running in the background.
>
>
Thank you.
Another question that I would like to ask:
Is there any downside just adding (executing) the sudo ./bin/weewxd
weewx.conf script to the /etc/rc.locatl file?
So my WeeWx installation gets started everytime on startup of my system.
In the Docs this instruction is given:
cd
Looking for someone to help with a realtime project I am looking at
completing. I have a running system that produces archive records and page
updates every 60 seconds but I need faster page updates, on the order of
5-10 seconds. I have looked at MQTT and some of the other options to create
