Would it be feasable to add locking to SessDBM such that we have
multiple readers and one writer to the DBM file? The session
database doesn't need any relational features, and the related bloat and
bugs. Look at what it takes just to set up a reliable database connection.
===
Archive at
Hello Dan -
DBM locking is not supported and we find that most Radiator users have
an SQL database for billing and customer management already, so an SQL
session database (which supports locking, multiple access, etc.) tends
to make more sense.
I've copied Mike on this mail as he may have
Hugh Irvine wrote:
Hello Dan -
DBM locking is not supported and we find that most Radiator users have
an SQL database for billing and customer management already, so an SQL
session database (which supports locking, multiple access, etc.) tends
to make more sense.
Hi Hugh.
We use LDAP
Hi All,
Im pleased to report that this problem was due to an incompatibility
introduced in the latest freetds 0.61 snapshot. When Tim rolled back to the
stable 0.60 release, it worked fine.
Cheers, and thanks to Tim for his patience.
On Fri, 7 Feb 2003 12:50 pm, Tim Jung wrote:
Yes I can go
Ok I found out that there are significant changes in the up coming FreeTDS
v0.61. If you ask either the DBD-Sybase author about what to run he will
tell you to run DBD-Sybase v0.95 and then he and the FreeTDS guys will tell
you if your running that version of DBD-Sybase you should be running the
Denis Pavani asked:
Does anyone know if Radiator supports WEP key rotation on 802.1x sessions?
Yes, Radiator supports dynamic WEP keys for a number of EAP 802.1x
authentication protocols, specifically for
TLS
TTLS
PEAP and
SIM (forthcoming)
when the AutoMPPEKeys parameter is enabled.