as i understand it, the "systemd way" is one of these two: 1) override. to change behavior of a systemd unit that was installed by a deb/rpm package, use the ".d" pattern.
in this case, create the overrides directory: sudo mkdir /etc/systemd/system/weewx.service.d then put this into the file /etc/systemd/system/weewx.service.d/waitfornetwork.conf [Unit] Wants=network-online.target After=network-online.target 2) modify. to change the beavior of a systemd unit that was installed by the user/sysadmin, modify the systemd unit in /etc/systemd/system in this case, add two lines to the [Unit] section of /etc/systemd/system/weewx.service Wants=network-online.target After=network-online.target the other pattern is to use environment variables, but (a) systemd explicitly discourages doing that the standard way by using /etc/default (any linux) or /etc/sysconfig (redhat-specific), and (b) the weewx devs prefer to have everything in a single conf file since environment variables can be difficult to diagnose/support. i have not done extensive testing with either (1) or (2) above, so apologies for providing examples without solid testing. but there are just too many systemd variations out there. maybe when systemd has gotten past its toddler years... m -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0edd7cdb-5247-45a1-89d6-2e8086cf4f44n%40googlegroups.com.
