Conflicts:
	smradiusd

Robert Anderson authored 13 years ago and Nigel Kukard committed 13 years ago

Using the attribute SMRadius-Username-Transform set for the configuration stage, a username sent by a client can be transformed using the attribute value, eg. @current=@replacement.

- Use accounting summaries
- Added alot of debugging
- Various other cleanups

Added cleanup priority

Added cleanup priority

Added better logging support
Allow the use of a date to clean up for on the commandline

Base second datetime object off the first, but use ->truncate instead. This passes the timezone to the next object via clone().

TYPE was removed and replaced by ENGINE in mysql 5.5

Incorrect hash ref element was making cache time for get usage and user data lookup default back to 300 (default)

Use formatted Timestamp element instead of Timestamp-Unix when inserting and updating the same way accounting is done.

If its missing its not a train smash, can be someone just enabled
the feature.

Added cleanup functionality to remove old user data if the user no longer exists

When enabled mod_feature_validity will now check if the time since first successful connect until now is more than the allowed value set using the SMRadius-Validity-ValidWindow attribute.

Make sure we standardize how the database columns are cased. The only
real impact of this change is userdb.id becomes userdb.ID as this was
the only variable affected.

mysql> select * from users_data;
+----+--------+-------------+-------------------------------------------------+--------------+
| ID | UserID | LastUpdated | Name                                            | Value        |
+----+--------+-------------+-------------------------------------------------+--------------+
| 25 |      1 |  1301180792 | global/FirstLogin                               | 1301180792   |
+----+--------+-------------+-------------------------------------------------+--------------+
1 row in set (0.00 sec)

This module create the following users_data entries...
mysql> select * from users_data;
+----+--------+-------------+-------------------------------------------------+--------------+
| ID | UserID | LastUpdated | Name                                            | Value        |
+----+--------+-------------+-------------------------------------------------+--------------+
| 26 |      1 |  1301181002 | mod_feature_user_stats/CurrentMonthTotalTraffic | 1            |
| 27 |      1 |  1301181002 | mod_feature_user_stats/CurrentMonthTotalUptime  | 244          |
| 28 |      1 |  1301181002 | mod_feature_user_stats/NAS-Identifier           | Neemo        |
| 29 |      1 |  1301181002 | mod_feature_user_stats/Framed-IP-Address        | 192.168.0.99 |
+----+--------+-------------+-------------------------------------------------+--------------+
4 rows in set (0.00 sec)

Added to config file

Fixed bug in config file regarding users_data query

- Better describe functions
- Formatting fixups
- Use better cached variable names
- Fixed bug where wrong cached time variable was being used
- Set cache dataset name to something more meaningful
- Database column names are lowercase not upper case , this must be fixed though

Better support for globally unique user data caching.