(RADIATOR) Use single <Handler> or multiple <Handler> statements?

[Hugh Irvine]

Hello Elias -

In your case I would do this:

# define Client clauses with Identifiers

<Client a.a.a.a>
	Identifier WhatEver
	.....
</Client>

<Client b.b.b.b>
	Identifier WhatEver
	.....
</Client>

<Client c.c.c.c>
	Identifier WhatEver
	.....
</Client>

<Client d.d.d.d>
	Identifier WhatEver
	.....
</Client>

<Client e.e.e.e>
	Identifier WhatEver
	.....
</Client>

.....

# define Handlers

<Handler Client-Identifier = WhatEver>
	.....
</Handler>


regards

Hugh


On Tuesday, Nov 26, 2002, at 17:11 Australia/Melbourne, Elias wrote:

> Hi Hugh,
>  
> Will there be any performance difference if I structure my config file 
> as below?
>  
> a. <Handler NAS-IP-Address = /a.a.a.a|b.b.b.b|c.c.c.c|d.d.d.d|e.e.e.e/>
>  
> b. <Handler NAS-IP-Address =/a.a.a.a/>
>     <Handler NAS-IP-Address =/b.b.b.b/>
>     <Handler NAS-IP-Address =/c.c.c.c/>
>     <Handler NAS-IP-Address =/d.d.d.d/>
>     <Handler NAS-IP-Address =/e.e.e.e/>
>  
> Which way would be faster/better for Radiator? Or will both of them 
> just give the same results? Thanks.
>  
>  
> - Elias -
> ----------------------------------------- (on inetxys)
>
> email-body was scanned and no virus found
> email-body was scanned and no virus found
> ---------------------------------------------------------
>

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.