8cbc68f28f
Historically there were plenty of callback based implementations around ifupdown via /etc/network/if-up and similar. NetworkManager added the dispatcher [1] feature for such a kind of functionality. But so far a systemd-networkd (only) systemd had no means to handle those cases. This is solved by networkd-dispatcher which is currently available at least in ArchLinux and Ubuntu. It takes away the responsibility to listen on netlink events in each application and provides a more classic script-drop-in interface to respond to networkd events [3]. This commit makes the NM example compatible to be used by NetworkManager dispatcher as well as by networkd-dispatcher. That way we avoid too much code duplication and can from now on handle special cases in the beginning so that the tail can stay commonly used. After discussion on IRC the current check differs by checking the argument count (only in NetworkManager), if ever needed we could extend that to check for known custom environment vars (NetworkManager => CONNECTION_UUID; networkd-dispatcher => OperationalState). [1]: https://developer.gnome.org/NetworkManager/stable/NetworkManager.html [2]: https://github.com/craftyguy/networkd-dispatcher [3]: https://github.com/systemd/systemd/blob/master/src/systemd/sd-network.h#L86 Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com> |
||
|---|---|---|
| .. | ||
| chrony-wait.service | ||
| chrony.conf.example1 | ||
| chrony.conf.example2 | ||
| chrony.conf.example3 | ||
| chrony.keys.example | ||
| chrony.logrotate | ||
| chrony.nm-dispatcher | ||
| chrony.spec | ||
| chronyd.service | ||