krb5 commit: Exit with status 0 from kadmind

https://github.com/krb5/krb5/commit/3e53f7b254c6704ad16942f98d9b222c9e069ef3
commit 3e53f7b254c6704ad16942f98d9b222c9e069ef3
Author: Robbie Harwood <[email protected]>
Date:   Wed Mar 14 14:31:22 2018 -0400

    Exit with status 0 from kadmind
    
    Typically, 0 denotes successful exit.  In particular, init systems
    will complain if another different value is returned.  This presents a
    problem for automated installation jobs which want to restart kadmind.
    
    `service kadmin stop` typically sends SIGTERM, which is caught by
    verto and passed to our handler.  Besides cleanup, we then call
    verto_break(), which causes the verto_run() event loop to return.  The
    weird return code has been present since the addition of the kadmin
    code, which used a similar event model for signals.
    
    ticket: 8650 (new)

 src/kadmin/server/ovsec_kadmd.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/kadmin/server/ovsec_kadmd.c b/src/kadmin/server/ovsec_kadmd.c
index 6c87590..936955b 100644
--- a/src/kadmin/server/ovsec_kadmd.c
+++ b/src/kadmin/server/ovsec_kadmd.c
@@ -560,5 +560,5 @@ main(int argc, char *argv[])
 
     krb5_klog_close(context);
     krb5_free_context(context);
-    exit(2);
+    exit(0);
 }