41 lines
1.4 KiB
Plaintext
41 lines
1.4 KiB
Plaintext
{
|
|
# MODULE CONFIGURATION
|
|
#
|
|
# The names and configuration of each module is located in this section.
|
|
#
|
|
# After the modules are defined here, they may be referred to by name,
|
|
# in other sections of this configuration file.
|
|
}
|
|
modules \{ {
|
|
#
|
|
# Each module has a configuration as follows:
|
|
#
|
|
# name [ instance ] {
|
|
# config_item = value
|
|
# ...
|
|
# }
|
|
#
|
|
# The 'name' is used to load the 'rlm_name' library
|
|
# which implements the functionality of the module.
|
|
#
|
|
# The 'instance' is optional. To have two different instances
|
|
# of a module, it first must be referred to by 'name'.
|
|
# The different copies of the module are then created by
|
|
# inventing two 'instance' names, e.g. 'instance1' and 'instance2'
|
|
#
|
|
# The instance names can then be used in later configuration
|
|
# INSTEAD of the original 'name'. See the 'radutmp' configuration
|
|
# for an example.
|
|
#
|
|
|
|
#
|
|
# As of 3.0, modules are in mods-enabled/. Files matching
|
|
# the regex /[a-zA-Z0-9_.]+/ are loaded. The modules are
|
|
# initialized ONLY if they are referenced in a processing
|
|
# section, such as authorize, authenticate, accounting,
|
|
# pre/post-proxy, etc.
|
|
#
|
|
}
|
|
$INCLUDE mods-enabled/
|
|
|