@@ -835,7 +835,7 @@ To populate this new configuration:
835
835
836
836
.. code-block :: console
837
837
838
- $ sysrepocfg -d startup -f xml -m kea-dhcp6-server --edit =startup.xml
838
+ $ sysrepocfg -d startup -f xml -m kea-dhcp6-server --import =startup.xml
839
839
840
840
:iscman: `kea-netconf ` pushes the configuration found in the Sysrepo startup
841
841
datastore to all Kea servers during its initialization phase, after it
@@ -900,7 +900,7 @@ It is directly rejected by ``sysrepocfg``:
900
900
901
901
.. code-block :: console
902
902
903
- $ sysrepocfg -d running -f xml -m kea-dhcp6-server --edit =BAD-schema.xml
903
+ $ sysrepocfg -d running -f xml -m kea-dhcp6-server --import =BAD-schema.xml
904
904
905
905
In the second case, the configuration is rejected by :iscman: `kea-netconf `.
906
906
For example, consider this ``BAD-translator.xml `` file:
@@ -993,7 +993,7 @@ This configuration is installed by:
993
993
994
994
.. code-block :: console
995
995
996
- $ sysrepocfg -d running -f xml -m kea-dhcp6-server --edit =twopools.xml
996
+ $ sysrepocfg -d running -f xml -m kea-dhcp6-server --import =twopools.xml
997
997
998
998
.. _operation-example-2subnets :
999
999
@@ -1036,7 +1036,7 @@ This configuration is installed by:
1036
1036
1037
1037
.. code-block :: console
1038
1038
1039
- $ sysrepocfg -d running -f xml -m kea-dhcp6-server --edit =twosubnets.xml
1039
+ $ sysrepocfg -d running -f xml -m kea-dhcp6-server --import =twosubnets.xml
1040
1040
1041
1041
.. _operation-example-logging :
1042
1042
@@ -1155,5 +1155,5 @@ are done at the same configuration state and that no change happens between expo
1155
1155
1156
1156
.. code-block :: console
1157
1157
1158
- $ sysrepocfg --datastore running --edit =save.xml
1159
- $ sysrepocfg --datastore startup --edit =save.xml
1158
+ $ sysrepocfg --datastore running --import =save.xml
1159
+ $ sysrepocfg --datastore startup --import =save.xml
0 commit comments