The gdbm-Realm

This realms use gdbm als "Database" for the radiusd. The Reply-Part is in the memory in the form it will send, so there is simply a memcpy from the database-buffer to the message-buffer. The usage of gdbm is fast, but have some Problems. gdbm allows many Processes to read or one to write. The locking is done when the process starts. If the Radiusd runs, I couldn't make new users. This realms are enhanced with administration-service, so that the radiusd is the only process that is writing.

But these ideas to overcome this limits, and are not good any more.

Tools for Administration

baueuserdb gdbmfile [userprofile-file]: generates a userdb from a cache-file. A usersfile is for backwardcompatibily also accepted
listuserdb [--reo]radiusdb: lists all usernames in the gdbm-userfile to the standartoutput (This can used only when the radiusd is not alive)
The option --reo reorganises the Radius-gdbm.hashtabe by thowing out timed-ount Uers and calling the reorganising-Routine of gdbm(3)
userquery: is for query the gdbm-userfile (This can used only when the radiusd is not alive).

Clients for Administration

radadmin: adds,overwrites,updates,deletes a User from/to/in the Radiusdatabase. Another options is to list the active users or the Record of a single user.