Alexander M. Pravking [EMAIL PROTECTED] wrote:
By the way, %{Simultaneuos-Use} will not work, since there's no way to
expand check items from the request...
Nonsense. See 'doc/variables.txt'
Huh?
Hmm... if it's not there, then it's trivial enough to add. ~10
lines in
On Tue, Jul 29, 2003 at 10:52:59AM -0400, Alan DeKok wrote:
Alexander M. Pravking [EMAIL PROTECTED] wrote:
By the way, %{Simultaneuos-Use} will not work, since there's no way to
expand check items from the request...
Nonsense. See 'doc/variables.txt'
Huh?
Hmm... if
On Mon, Jul 28, 2003 at 02:02:22PM -0400, Alan DeKok wrote:
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
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:
On Mon, Jul 28, 2003 at 02:02:22PM -0400, Alan DeKok wrote:
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
Alexander M. Pravking [EMAIL PROTECTED] wrote:
By the way, %{Simultaneuos-Use} will not work, since there's no way to
expand check items from the request...
Nonsense. See 'doc/variables.txt'
How about, say, new integer attribute like FreeRADIUS-Reply-Code,
which will be automatically
On Mon, Jul 28, 2003 at 08:11:26PM -0400, Alan DeKok wrote:
Alexander M. Pravking [EMAIL PROTECTED] wrote:
By the way, %{Simultaneuos-Use} will not work, since there's no way to
expand check items from the request...
Nonsense. See 'doc/variables.txt'
Huh?
%{Attribute-Name}
On Sat, Jul 26, 2003 at 07:09:38PM -0700, Alex Chen wrote:
I finally get the counter module to work but there is a small question
about the reply message issued by the counter when the accumulated time
exceeds
the value of the 'check-name' attribute. I set the 'reset' to 'never' and
when the
I finally get the counter module to work but there is a small question
about the reply message issued by the counter when the accumulated time
exceeds
the value of the 'check-name' attribute. I set the 'reset' to 'never' and
when the limit, say, 60 seconds, is reached, the reply message says:
