Yep! That's it. THANKS! I installed it using the DEB package. Later I was
warned away from it but I had already got it running so I never
re-installed it via the setup.py
On Thursday, September 8, 2016 at 10:40:35 AM UTC-4, Macha wrote:
>
> I think it depends on the way you installed it. With
I think it depends on the way you installed it. With my Pi, it shows it
running as a python task. I always do ..
ps aux | grep wee
.. and it shows the command launching weewx, something like ...
root 4193 13.9 5.4 78352 48232 ?Sl Sep06 398:00 python
./bin/weewxd weewx.conf
I
This is what I get with the ps -a command. For some reason the weewx
process does not show up?
pi@WXraspberrypi:/ $ ps -a
PID TTY TIME CMD
933 tty1 00:00:00 bash
3310 pts/200:00:00 ps
20632 pts/000:00:00 sudo
20636 pts/000:00:00 tail
On Thursday, September 8, 2016
THANK YOU!
On Wednesday, September 7, 2016 at 11:16:25 PM UTC-4, Dave Webb wrote:
>
> You need to stop and restart weewx for it to pick up the changes in
> weewx.conf
>
> Dave-KB1PVH
>
> Sent from my Galaxy S7
>
> On Sep 7, 2016 11:15 PM, "Jim W." >
> wrote:
>
>> Does the config file get read on
Or you can force a .conf reload with a hup
"
You can tell a running instance of weewx to reread its configuration file
by sending it the HUP signal. First run ps to find out the Process ID (PID)
number of the instance, then send it the HUP signal:
ps -a # Note the PID of the weew
You need to stop and restart weewx for it to pick up the changes in
weewx.conf
Dave-KB1PVH
Sent from my Galaxy S7
On Sep 7, 2016 11:15 PM, "Jim W." wrote:
> Does the config file get read once during start up or is it poled
> continuously? If I make a change in the config file do I have to stop
