sql.conf vs. modules/sql

[Stefan Winter]

  Hi,

when setting up a brand-new server, I fell over one caveat (and did so 
more than once, actually): almost all modules are placed in modules/* 
and get get auto-loaded when they are needed by the actual configuration.

Except eap.conf and sql.conf - these need explicit $INCLUDEs in 
radiusd.conf.

I wonder why - couldn't sql.conf just become modules/sql? It's commented 
out anyway, so wouldn't get loaded with the default config. But it would 
enable auto-loading when uncommenting "sql" - making thinking of 
radiusd.conf obsolete.

What do you think?

(Same goes for eap.conf)

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473