Hello everyone - Just a note to let you know that we have now had several customers report problems using <SessionDatabase DBM> on Solaris. The symptoms are that Radiator appears to hang, although what is really happening is that it is looping in the DBM code. This only appears to occur when using the default 'AnyDBM_File' construct in SessDBM.pm. We have seen two different fixes so far, one is to use a different DBM library (Berkley was mentioned I believe) and the other was to move to a <SessionDatabase SQL>. If you want to change the behaviour of SessDBM.pm, you will first have to download the latest version from the Radiator 2.14.1 patches area and then edit the following to select an alternative DBM library: # This will cause perl to choose the 'best' DBM format available to # you. You can force it to use another format by setting $dbtype to # NDBM_File, DB_File, GDBM_File, SDBM_File or ODBM_File my $dbtype = 'AnyDBM_File'; require "$dbtype.pm"; best regards Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, NT, Rhapsody === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
