3.2. Including parts of configuration from external files

The include directive in the Radiator configuration file is followed by a file name. That external file is opened and read to the end as a configuration file before processing of the current configuration file continues. Special filename characters are permitted (for more information, see Section 3.3. Special formatters). Files can be recursively included to any depth. The include keyword is case insensitive, here are examples, which are both correct:
include %D/clients.cfg
Include %D/realms.cfg
Filename can include csh(1) style wildcards and expansions such as *, ?, [...], {....}, ~, and so on. Files whose first character is a '.' are ignored unless explicitly matched. Wildcard files are included in lexicographic order of their filename. Here are examples of using wildcards:
# Reads all files with a .cfg extension:
include %D/*.cfg
# Matches radiator1.cfg, radiator2.cfg etc:
include /etc/radiator/radiator[0123456].cfg
You can also use the include mechanism to capture the output of a script. A program name followed by a vertical bar runs the named program and includes its output into the configuration file. This is a useful way for generating some or all of your Radiator configuration programmatically. For example, you can write a script to generate all your <Client> clauses by processing some external description of all your NASs. Here is an example of running a program:
include %D/myClientScript.pl|