This patch inclues

* New data types 

  "Total queued logfile" and "Individual queued logfile" based on
  FLEXlm debug log files can now be generated.

* Update data type

  "Total license logfile" data type now has "Max available licenses"
  classification and "Max, Min and Avg. utilization" measurements.

* Improved FLEXlm debug log processing (FLC2)

  Flab is now run automatically by the server. Processing of data
  now correctly handles crossing of day boundaries.

* New and improved data regeneration script

  The new script "regenerate_data" (which replaces the old
  regenerate_license_data script). The new script has more
  logical options and covers all data types that are
  handled by archiver/filtrator

An bug in filtrator causes problems when processing data
from more than one license type, E.g both "flex" and "lum"
data for the same period.

Please note that the new filtrator now requires multiple 
license clients for the same products to be setup with 
different offsets to guarantee correct behaviour, e.g if 
you have two clients for a set of products, one should be
setup without offset and the other with an offset set to 
half the polling interval.

Error in filter definition gives occational wrong calculation
of Active Time.

Fix bug when calculating week of first year when first days
in the week belongs to the previous year.

Some more FLEXlm debug lines that needs to be ignored:

  20:28:28 (lmgrd) Message volume in last 6 hours:
  20:28:28 (lmgrd)        1337 max msgs per minute, 26281 total msgs

Lines with incomplete timestamp, e.g like

    :39:08 (lmgrd) Retrying socket bind (address in use: port 27182)

is also ignored.

In addition a two bugs in filtrator was fixed:

 - Debug events between start of hour and first polling
   where somtimes doubled.
 - Data for hour 23 was skipped

Bug in filtrator caused error when calculating elapsed time for
hour 23 every day.

Some lines in the FLEXlm debug lines have the wrong time stamp.
This patch makes the filtrator ignore these lines.

Filtrator had problem with handling time zone correctly
when timzone differents from GMT was high