using systemd, i start weewx instances independently. my [email protected] file uses the unit name as the weewx conf file e.g. # systemctl start weewx@gw1000 → starts ‘weewxd gw1000.conf’ (and similarly for pidfiles etc). i also keep separate logs for instances e.g. weewxd gw1000.conf —log-name=weewx-gw1000 with rsyslog routing weewx-gw1000 to /var/log/weewx/gw1000.log. you can wildcard the unit name e.g. # systemctl status weewx@* ⊣ Graham Eddy ⊢
> On 25 Mar 2022, at 3:19 am, matthew wall <[email protected]> wrote: > > finally, it is my intent to push the capabilities of weewx-multi into the > 'standard' weewx init.d script, and make the package installers detect > whether to deploy an rc script or a systemd unit file. that is complicated > by the fact that (1) there are (were) different conventions for init scripts > on redhat vs debian vs suse vs *bsd, and (2) we now have to keep systemd > happy too, which means doing a variation of the weewx unit file that has > weewx-multi capabilities (perhaps kinda like openvpn has done). -- 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/6882B729-8DA1-4EEF-B2D3-46BA0224EA56%40gmail.com.
