Fix text and test

defaults/krill-pubd.conf

@@ -8,12 +8,10 @@
 #
 # Currently, Krill supports disk based storage only.
 #
-# You MUST ensure that only one Krill node using this storage is
-# active at any given moment. Under the hood, lockfiles are used
-# to prevent concurrency issues, and if you should use a shared
-# disk then it may not be guaranteed that lockfiles are seen
-# by all nodes in time. You can however, use a shared filesystem
-# and have one standby node.
+# You can use a shared disk and a standby Krill node for redundancy.
+# However, data corruption issues can occur if you run multiple active
+# Krill nodes using a shared disk. Therefore, you MUST ensure that only
+# one Krill node is active at any given time.
 #
 # Example configurations:
 # storage_uri = "/var/lib/krill/data/"

defaults/krill-testbed.conf

@@ -38,12 +38,10 @@
 #
 # Currently, Krill supports disk based storage only.
 #
-# You MUST ensure that only one Krill node using this storage is
-# active at any given moment. Under the hood, lockfiles are used
-# to prevent concurrency issues, and if you should use a shared
-# disk then it may not be guaranteed that lockfiles are seen
-# by all nodes in time. You can however, use a shared filesystem
-# and have one standby node.
+# You can use a shared disk and a standby Krill node for redundancy.
+# However, data corruption issues can occur if you run multiple active
+# Krill nodes using a shared disk. Therefore, you MUST ensure that only
+# one Krill node is active at any given time.
 #
 # Example configurations:
 # storage_uri = "/var/lib/krill/data/"

defaults/krill.conf

@@ -8,12 +8,10 @@
 #
 # Currently, Krill supports disk based storage only.
 #
-# You MUST ensure that only one Krill node using this storage is
-# active at any given moment. Under the hood, lockfiles are used
-# to prevent concurrency issues, and if you should use a shared
-# disk then it may not be guaranteed that lockfiles are seen
-# by all nodes in time. You can however, use a shared filesystem
-# and have one standby node.
+# You can use a shared disk and a standby Krill node for redundancy.
+# However, data corruption issues can occur if you run multiple active
+# Krill nodes using a shared disk. Therefore, you MUST ensure that only
+# one Krill node is active at any given time.
 #
 # Example configurations:
 # storage_uri = "/var/lib/krill/data/"

test-resources/krill-init-multi-user.conf

@@ -8,12 +8,10 @@
 #
 # Currently, Krill supports disk based storage only.
 #
-# You MUST ensure that only one Krill node using this storage is
-# active at any given moment. Under the hood, lockfiles are used
-# to prevent concurrency issues, and if you should use a shared
-# disk then it may not be guaranteed that lockfiles are seen
-# by all nodes in time. You can however, use a shared filesystem
-# and have one standby node.
+# You can use a shared disk and a standby Krill node for redundancy.
+# However, data corruption issues can occur if you run multiple active
+# Krill nodes using a shared disk. Therefore, you MUST ensure that only
+# one Krill node is active at any given time.
 #
 # Example configurations:
 # storage_uri = "/var/lib/krill/data/"
@@ -464,6 +462,7 @@ service_uri = "https://localhost:3001/"
 # timing_roa_reissue_weeks_before = 4
 
 
+
 ######################################################################################
 #                                                                                    #
 #               ----==== WEB UI MULTI-USER LOGIN CONFIGURATION ====----              #
@@ -1019,4 +1018,4 @@ service_uri = "https://localhost:3001/"
 # Also note that, while not visible in the configuration above, the GCP OpenID
 # Connect provider advertizes an RFC 7009 OAuth 2.0 Token Revocation compatible
 # `revocation_endpoint` which Krill will use to revoke the Google login token
-# when the user logs out of Krill.
+# when the user logs out of Krill.

test-resources/krill-init.conf

@@ -8,12 +8,10 @@
 #
 # Currently, Krill supports disk based storage only.
 #
-# You MUST ensure that only one Krill node using this storage is
-# active at any given moment. Under the hood, lockfiles are used
-# to prevent concurrency issues, and if you should use a shared
-# disk then it may not be guaranteed that lockfiles are seen
-# by all nodes in time. You can however, use a shared filesystem
-# and have one standby node.
+# You can use a shared disk and a standby Krill node for redundancy.
+# However, data corruption issues can occur if you run multiple active
+# Krill nodes using a shared disk. Therefore, you MUST ensure that only
+# one Krill node is active at any given time.
 #
 # Example configurations:
 # storage_uri = "/var/lib/krill/data/"