It is modular and right now it assumes that user information is stored in an ldap server
or an sql database and accounting in an sql server.
+Extra documentation from Stadler Karel (<Karel.Stadler@psi.ch>):
+http://kstadler.ch/index.php?topgroupid=1&subgroupid=14&groupid=11
+
+There is also a nice HOWTO in the doc folder
+
+
INSTALLATION:
Put dialup_admin in /usr/local/dialupadmin
* bin/clean_radacct: It will delete all entries in the radacct table with a starttime > 1 day and
stoptime = 0. It will not do an harm even if it deletes valid entries since radiusd will fall
back to insert if update fails.
+* bin/truncate_radacct: It will delete sessions from the radacct table which are older than a configurable
+ number of days
+* bin/tot_stats: Update the totacct table with aggregated daily accounting information for each user.
+ We keep a row per user for each day.
+* bin/monthly_tot_stats: Log in the mtotacct table aggregated accounting information for each user spaning
+ in one month period. If the current month has not ended it will log information up to the current month day
+
+
The structure of the tree is:
htdocs:: user_finger.php3 =>
It will finger the nas(es) and show the logged in users. If an argument server is passed then
it will only show users for the specific access server.
+ If an argument usage_summary is passed then it will only show a line like:
+ "Online: <num> Free: <num>" which can be used by other pages
+htdocs::failed_logins.php3 =>
+ It will show all the failed logins as logged in the radacct table by the log_badlogins script
html:: Contains the html code for a few pages
html::user_admin.html.php3 =>