daemon: Promote debug messages about --start-as-* to NOTICE level

It is important to know when ctdbd is started with --start-as-stopped
or --start-as-disabled.  Given that this only happens once it makes
sense to promote these debug items to NOTICE level.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
(Imported from commit eb159f3ff530de8828631b04e17bf0990aed906e)

diff --git a/server/ctdb_daemon.c b/server/ctdb_daemon.c
index fe995c6c780d2b666c97ab206eaf68269053f75a..f0920c51c133e2fb5f0418c92d8563529197f7a1 100644 (file)
--- a/server/ctdb_daemon.c
+++ b/server/ctdb_daemon.c
@@ -1024,12 +1024,12 @@ static void initialise_node_flags (struct ctdb_context *ctdb)
 
        /* do we start out in DISABLED mode? */
        if (ctdb->start_as_disabled != 0) {
-               DEBUG(DEBUG_INFO, ("This node is configured to start in DISABLED state\n"));
+               DEBUG(DEBUG_NOTICE, ("This node is configured to start in DISABLED state\n"));
                ctdb->nodes[ctdb->pnn]->flags |= NODE_FLAGS_DISABLED;
        }
        /* do we start out in STOPPED mode? */
        if (ctdb->start_as_stopped != 0) {
-               DEBUG(DEBUG_INFO, ("This node is configured to start in STOPPED state\n"));
+               DEBUG(DEBUG_NOTICE, ("This node is configured to start in STOPPED state\n"));
                ctdb->nodes[ctdb->pnn]->flags |= NODE_FLAGS_STOPPED;
        }
 }