If you are changing the config file I would like to see an $INCLUDE for my.modules, my.authorization, my.accounting ... at the beginning of each section so I can make sure my configurations are what's causing problems with new versions. If I can install freeradius and touch an empty my.whatever.file and it works it's easy to know where to start looking. It's not a bug or enhancement it's just easier for users. Alan DeKok wrote:
Nicolas Baradakis <nbk@sitadelle.com> wrote:
The Debian package already sets the raddbdir to "/etc/freeradius". Of course it's OK for me to rename "radiusd.conf" to "freeradius.conf", too. The only problem I see is it may rise many questions on the users mailing list.
Leave the stuff that gets mangled by "configure" in radiusd.conf, and put comments at the start saying "just an include file... look elsewhere".
freeradiusd.conf can then just $INCLUDE radiusd.conf, and then we don't need a freeradiusd.conf.in.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html