Blame SOURCES/Exit-with-status-0-from-kadmind.patch

167778
From f77de343e052ad66324eda13cf8dd9b9e131590c Mon Sep 17 00:00:00 2001
167778
From: Robbie Harwood <rharwood@redhat.com>
167778
Date: Wed, 14 Mar 2018 14:31:22 -0400
167778
Subject: [PATCH] Exit with status 0 from kadmind
167778
167778
Typically, 0 denotes successful exit.  In particular, init systems
167778
will complain if another different value is returned.  This presents a
167778
problem for automated installation jobs which want to restart kadmind.
167778
167778
`service kadmin stop` typically sends SIGTERM, which is caught by
167778
verto and passed to our handler.  Besides cleanup, we then call
167778
verto_break(), which causes the verto_run() event loop to return.  The
167778
weird return code has been present since the addition of the kadmin
167778
code, which used a similar event model for signals.
167778
167778
(cherry picked from commit f970ad412aca36f8a7d3addb1cd4026ed22e5592)
167778
(cherry picked from commit 3bfe632c7011c335362d78356232507d9ee26f73)
167778
---
167778
 src/kadmin/server/ovsec_kadmd.c | 2 +-
167778
 1 file changed, 1 insertion(+), 1 deletion(-)
167778
167778
diff --git a/src/kadmin/server/ovsec_kadmd.c b/src/kadmin/server/ovsec_kadmd.c
167778
index a3edd3b00..9fc49f1e6 100644
167778
--- a/src/kadmin/server/ovsec_kadmd.c
167778
+++ b/src/kadmin/server/ovsec_kadmd.c
167778
@@ -558,5 +558,5 @@ main(int argc, char *argv[])
167778
 
167778
     krb5_klog_close(context);
167778
     krb5_free_context(context);
167778
-    exit(2);
167778
+    exit(0);
167778
 }