Thomas Haller e447af8d35 cloud-setup: let dispatcher script run tool only if service is enabled ... We don't want that when the user installs the package, that the dispatcher script automatically executes the tool. Instead, the user should use `systemctl enable/disable` to control whether the service is active (of via the timer). Hence, let the dispatcher script check whether the service is enabled. That leads to a different problem, that we need to make it possible for "nm-cloud-setup.service" to be enabled in the first place. As such, add a [Install] section and let it be wanted by NetworkManager.service. The problem with this is that now the tool will run very early, just after NetworkManager started. At that point, it might not yet have setup networking. But that should be acceptable, after all, the tool either fails to fetch meta data that early, or it succeeds. Very likely, it will by aborted by dispatcher's restart command. (cherry picked from commit 953e01336a)		2019-12-03 16:27:43 +01:00
..
cli	all: add device carrier flag	2019-11-22 10:18:27 +01:00
cloud-setup	cloud-setup: let dispatcher script run tool only if service is enabled	2019-12-03 16:27:43 +01:00
common	libnm: add ipvx.dhcp-hostname-flags properties	2019-11-28 17:56:35 +01:00
tests	libnm: add ipvx.dhcp-hostname-flags properties	2019-11-28 17:56:35 +01:00
tui	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
meson.build	cloud-setup: add tool for automatic IP configuration in cloud	2019-11-28 19:52:18 +01:00
nm-online.c	all: manually drop code comments with file description	2019-10-01 07:50:52 +02:00