Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 243668 - Wrong init script
Wrong init script
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: freeradius (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: John Dennis
Depends On: 243667
  Show dependency treegraph
Reported: 2007-06-11 08:03 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-01-07 18:11:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Marciniszyn 2007-06-11 08:03:29 EDT
+++ 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):

How reproducible:

Steps to Reproduce:
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:

For an example of the script that returns the error codes correctly and always
runs status see:

This bug is tracked by 237789.
Comment 1 Red Hat Bugzilla 2007-09-17 01:20:01 EDT
transferred from Thomas Woerner to John Dennis, requested by Steve Grubb.
Comment 2 John Dennis 2010-01-07 18:11:58 EST
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).

Note You need to log in before you can comment on or make changes to this bug.