Description of problem: krb5 init scripts (kadmin/krb5kdc/krb524) contain incorrect error codes that also prevent correct invocation of status command. For example [ ${NETWORKING} = "no" ] && exit 0 appears in all scripts, also if [ ! -f /var/kerberos/krb5kdc/principal ] ; then echo $"Error. Default principal database does not exist." exit 0 fi is not correct... There are more constructions like these in all three scripts. Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: When fixing this bug, please obbey our init script guidelines and be sure that status command is run correctly. Our guidelines are on following two pages: http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html http://intranet.corp.redhat.com/ic/intranet/InitscriptGuidelines.html For an example of the script that returns the error codes correctly and always runs status see: http://devserv.devel.redhat.com/~mmarcini/amd This bug is tracked by 237789.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
The bug also applies to kprop init script...
Do you have a patch?
Created attachment 239191 [details] tgz file with diffs of krb5 init scripts
In the future, please use unified (-u) format when providing patches -- they provide filenames and context which are both useful if there are any problems applying the patches.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0381.html