"Alexander M. Pravking" <[EMAIL PROTECTED]> wrote:
> Yeah, it's not the only place where configurable messages could be
> useful. I've already suggested such a thing, but the silence was an
> answer...
...
> Dear developers, how about customizable messages? Something like
> this in radiusd.conf:
>
> messages {
> multiple_login = "You are already logged in %{Simultaneous-Use} times\r\n"
> timespan_violation = "You are calling outside allowed timespan\r\n"
> ...
>}
Sure.
> I probably could work on that, but I need some guidelines:
> 1. Should it be a set of static variables, or searchable list like
> dictionary?
I'm not sure what you mean by that.
> 2. Should it be per-module configuration, or global?
Many messages are global. They should be in a global config.
> 3. Where to put these parameters in config?
In a new 'messages' block.
> 4. Recommended naming conventions?
Something short, but long enough to be reasonably obvious.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
