Salut Christophe -
It has always been the case that if you do not specify a session database in a Realm or Handler, the default is to use the last session database defined. I always find it easier to use Identifiers as you have in your second example. regards Hugh On Wed, 27 Mar 2002 18:22, Christophe Wolfhugel wrote: > Not sure this is a new feature or a bug. > > Here is an excerpt on my radius.cfg : > > <SessionDatabase NULL> > </SessionDatabase> > > <SessionDatabase SQL> > Identifier adsl > </SessionDatabase> > > <Handler Realm=/\.fsa$/, Client-Identifier=lns> > AcctLogFileName %L/%R/detail-lns > AccountingHandled > </Handler> > <Handler Realm=/\.fsa$/> > AcctLogFileName %L/%R/detail-lac > SessionDatabase adsl > AccountingHandled > </Handler> > > I happens that both handlers do now use the "adsl" SessionDatabase. > Is this desired ? By adding an identifier null session everything > goes back to normal : > > <SessionDatabase NULL> > Identifier nosess > </SessionDatabase> > > <Handler Realm=/\.fsa$/, Client-Identifier=lns> > AcctLogFileName %L/%R/detail-lns > SessionDatabase nosess > AccountingHandled > </Handler> -- 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 [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
