I suspect it is too difficult for automated install scripts to identify
multiple instances. My process is to
1. leave the weewx.conf setting as the demo DB and the service usually
disabled (not masked)
2. stop my two instances before installing.
3. upgrade.
4. check that the default service is running OK and the stop /disable it.
5. run diffs on any config file updates and if necessary apply them to
my other config files.
6. manually start each service
I cannot see how the postinstall code could cope with multi-instances when
based on systemd.
On Monday, 27 October 2025 at 4:15:05 am UTC+10 loeriver wrote:
> Hi,
> I upgraded weewx on Debian 12 (sudo apt update / upgrade) and noticed that
> after this a service "weewx" was running and my 2 instances that were
> running under 5.1 did not run anymore ("weewx@weather" and "weewx@wpm", 2
> customized configurations).
>
> Should such a case be handled by the standard update procedure or is this
> too special?
>
--
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 visit
https://groups.google.com/d/msgid/weewx-user/b5f1909e-512f-4843-9cae-427510f0dc72n%40googlegroups.com.
