[krbdev.mit.edu #8650] git commit

[Greg Hudson via RT]

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.

https://github.com/krb5/krb5/commit/3e53f7b254c6704ad16942f98d9b222c9e069ef3
Author: Robbie Harwood <rharwood at redhat.com>
Committer: Greg Hudson <ghudson at mit.edu>
Commit: 3e53f7b254c6704ad16942f98d9b222c9e069ef3
Branch: master
 src/kadmin/server/ovsec_kadmd.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)