Description of problem:
In order to synchronize the accounting of two radius peer servers one needs to
run the radrelay daemon. The freeradius RPM does contain the radrelay daemon but
lacks the init script to start it automatically at boot time.
Created attachment 125712 [details]
sample init script for radrelay
Quality Engineering Management has reviewed and declined this request. You may
appeal this decision by reopening this request.
It would be helpful if QEM had motivated why it has declined the request. Now I
have no other option than to appeal the decision.
My argument for inclusion of the radrelay init script is that Red Hat does
include the radrelay daemon in the RPM. This makes sense only if Red Hat
expects users to use radrelay. In that case an init script is essential.
Ergo, include both radrelay and an init script or neither.
Grrr, Bugzilla won't let me reopen the bug even though as the reporter I should
be allowed to reopen it.
Please regard comment #5 as an appeal to the decision.
User has requested reopening of this bug.
This bugzilla was marked for Fastrack which does not allow feature requests.
This is the reason that QE and naked it thus causing its closure. However in
further checking, I see that the freeradius component is an approved package for
RHEL 4.5. I removed the Fastrack flag and will ask QE to reconsider.
Thank you for bringing this issue to our attention.
transferred from Thomas Woerner to John Dennis, requested by Steve Grubb.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.