most cases, this reference will (of course) call the `radius` module.
In some cases, it is necessary to have module-specific policies. The
-xref:unlang/policy.d/policy_method.adoc[policy override] syntax allows
+xref:raddb/policy.d/method.adoc[policy override] syntax allows
for policies to be added around a module, or to override a module
method.
-In addition, the xref:unlang/policy.d/at_reference.adoc[@policy] references
+In addition, the xref:raddb/policy.d/at_reference.adoc[@policy] references
allow for policies to be placed in the module configuration file,
which helps to better organize module-specific configurations and
policies.
module configuration file.
[NOTE]
-===
+====
There is no functional difference between an `@policy`, and a policy
located in the `policy.d/` directory. The only difference is their
location in the file system.
-===
+====
The `@policy` functionality is used when it is necessary to "wrap" a
module in a policy not just once, but every time the module is called.
-=== Module Method Overrides
+== Module Method Overrides
Thge `@policy` syntax be used in conjunction with the
-xref:unlang/policy.d/method.adoc[method override] syntax to
+xref:raddb/policy.d/method.adoc[method override] syntax to
override a module, but only when it is called from a specific
processing section.
The combination of the `@policy`, `unlang` and
-xref:unlang/policy.d/method.adoc[override] allows for
+xref:raddb/policy.d/method.adoc[override] allows for
extremely complex policies to be created in a very simple manner.
== Worked Example
various configurations behave differently.
It is better instead to use the `@policy` syntax along with the
-xref:unlang/policy.d/method.adoc[method override] syntax, to
+xref:raddb/policy.d/method.adoc[method override] syntax, to
"wrap" the `sql` module in a xref:unlang/timeout.adoc[timeout]
section. Even better, this `@policy` can be listed in the `sql`
module configuration file, and does not need to be in the `policy.d/`