+++ This bug was initially created as a clone of Bug #243667 +++ Description of problem: The radiusd init script returns incorrect error codes and some constructions in it may cause non-calling of status command. For example: [ -f $RADIUSD ] || exit 0 [ -f $CONFIG ] || exit 0 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.
transferred from Thomas Woerner to John Dennis, requested by Steve Grubb.
Thank you for your bug report. The init script in Fedora (F-12) and the soon to be released new version of freeradius (e.g. freeradius2) in RHEL 5 have fixed the init script issues. I'm going to close this as WONTFIX because this was filed against RHEL 4 and this particular issue does not seem to warrant the costs associated with issuing a RHEL errata (especially since more current versions have addressed the issue).