| Overview |  |
Behaviours: application.
| load_tables/1 | Load RADIUS dictionaries from the default directory. |
| load_tables/2 | Load RADIUS dictionaries from a certain directory. |
| modules_ready/1 | Equivalent to modules_ready(self(), Modules). |
| modules_ready/2 | Announce request handler module availability. |
| statistics/1 | manipulate server statistics * reset: reset all counters to zero * pull: read counters and reset to zero * read: read counters. |
load_tables(Tables::[eradius_dict:table_name()]) -> ok | {error, {consult, eradius_dict:table_name()}}
Load RADIUS dictionaries from the default directory.
load_tables(Dir::file:filename(), Tables::[eradius_dict:table_name()]) -> ok | {error, {consult, eradius_dict:table_name()}}
Load RADIUS dictionaries from a certain directory.
modules_ready(Modules) -> any()
Equivalent to modules_ready(self(), Modules).
modules_ready(Pid, Modules) -> any()
Announce request handler module availability.
Applications need to call this function (usually from their application master)
in order to make their modules (which should implement the eradius_server behaviour)
available for processing. The modules will be revoked when the given Pid goes down.
statistics(X1) -> any()
manipulate server statistics * reset: reset all counters to zero * pull: read counters and reset to zero * read: read counters
Generated by EDoc, Feb 7 2018, 08:44:41.