Bug 242502

Summary:	Wrong init script
Product:	[Fedora] Fedora	Reporter:	Michal Marciniszyn <mmarcini>
Component:	krb5	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED RAWHIDE	QA Contact:	Brian Brock <bbrock>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	jplans, tvujec
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-03 15:47:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	242500
Bug Blocks:

Description Michal Marciniszyn 2007-06-04 15:38:09 UTC

+++ This bug was initially created as a clone of Bug #242500 +++

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.

Comment 1 Michal Marciniszyn 2007-06-05 11:43:53 UTC

The bug also applies to kprop init script...