RHEL Patches Broke FreeRADIUS

[McNutt, Justin M.]

...

*facepalm*

Yeah, that'd do it.  Much easier than what I was doing.

Thanks, Alan.  :)

--J

From: Alan DeKok <aland at deployingradius.com<mailto:aland at deployingradius.com>>
Reply-To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org<mailto:freeradius-users at lists.freeradius.org>>
Date: Sat, 3 Mar 2012 09:14:31 +0100
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org<mailto:freeradius-users at lists.freeradius.org>>
Subject: Re: RHEL Patches Broke FreeRADIUS

McNutt, Justin M. wrote:
I'd like to tackle this from the FreeRADIUS side rather than by reconfiguring rpm because I can think of other reasons why some idio^H^H^H^H well-meaning admin might stick a test file in there without realizing that it causes problems.  Switching to a site-specific module name (or some other method that allows FR to ignore the "extra" files) would prevent any such scenario.

  The "modules" directory is just a convention.  It can be changed.

  Instead, put the modules into raddb/missouri/ :)

  Change radiusd.conf to edit $INCLUDE modules/ to missouri/

  And the problem will go away.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html