summaryrefslogtreecommitdiff
path: root/ctdb/server/ctdb_daemon.c
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2013-06-30 17:43:52 +1000
committerAmitay Isaacs <amitay@gmail.com>2013-07-05 15:52:33 +1000
commitc327c91490e6dbc7451100afd341fbcfc5d31444 (patch)
tree58d160287b9815c3082c62b7d79bf199ff05820a /ctdb/server/ctdb_daemon.c
parentdbd1759eae8f701ef3fede0ff5f5e3f61e995c38 (diff)
downloadsamba-c327c91490e6dbc7451100afd341fbcfc5d31444.tar.gz
ctdbd: Avoid a core dump when "init" event fails
The "init" event only really fails in the scripts, which should log something useful on failure. Therefore, a core dump isn't terribly useful and sometimes attracts unwanted attention. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 3af2d833b63af9931792106db71797f3692669a8)
Diffstat (limited to 'ctdb/server/ctdb_daemon.c')
-rw-r--r--ctdb/server/ctdb_daemon.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/ctdb/server/ctdb_daemon.c b/ctdb/server/ctdb_daemon.c
index 478962d6246..7d49cd2a659 100644
--- a/ctdb/server/ctdb_daemon.c
+++ b/ctdb/server/ctdb_daemon.c
@@ -1216,7 +1216,7 @@ int ctdb_start_daemon(struct ctdb_context *ctdb, bool do_fork, bool use_syslog,
ctdb_set_runstate(ctdb, CTDB_RUNSTATE_INIT);
ret = ctdb_event_script(ctdb, CTDB_EVENT_INIT);
if (ret != 0) {
- ctdb_fatal(ctdb, "Failed to run init event\n");
+ ctdb_die(ctdb, "Failed to run init event\n");
}
ctdb_run_notification_script(ctdb, "init");