From 8d8c320b74dd6aadf17614fe4dcdae8b6470b3ea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Hugo=20H=C3=B6rnquist?= <hugo@lysator.liu.se>
Date: Wed, 27 Sep 2023 07:01:50 +0200
Subject: Clarify choice of reload method.

---
 manifests/networkd.pp | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/manifests/networkd.pp b/manifests/networkd.pp
index 7c06b58..e7db086 100644
--- a/manifests/networkd.pp
+++ b/manifests/networkd.pp
@@ -11,7 +11,13 @@ class networking::networkd (
     }
   }
 
-  # Why this instead of `networkctl reload`?
+  # Force a full restort of systemd networkd to reload all configuration.
+  # The alternative is to first run `networkctl reload` which reloads
+  # network files, followed by a `networkctl reconfigure <iface>`.
+  #
+  # When this was writen, I didn't realize that a reload +
+  # reconfigure was required. Note that old configurations might
+  # lingerif done that way.
   if $notify_ {
     exec { 'reload networkd':
       command     => 'systemctl reload-or-restart systemd-networkd',
@@ -25,4 +31,3 @@ class networking::networkd (
     enable => true,
   }
 }
-
-- 
cgit v1.2.3