- 2.1.10
  - e-Mail addresses changed to linecontrol@gmx.ch
  - Updated ./README file...
  - Added new centralized MySQL Backend. This should
    reduce or even eliminate the 'server has gone away'
	messages

- 2.1.9
  - MySQL logging didn't log when a connection got closed
    by the server. This should be fixed.
  - If mysql related keywords were found in linesrv.conf
    but mysql support was disabled while compiling then
	the server made a segfault. This should be fixed too.
  - We still have some problems regarding mysql logging.
    (the syslog messages "MySQL server has gone away")
	This means that certain things don't get logged...

- 2.1.8
  - MySQL logging didn't work in 2.1.7 (at least on my
    system it didn't work). Cleanup the code a little bit
	and made it working. Added a new table to the database
	(see ./config/complete_syntax/mysqldb.linesrv.dump, load
	that file with "mysql -u <admin-username> -p < 'filename'",
	don't load it if you've got already the linesrv database,
	then add the changes manually. e.g. look at
	mysqldb.linesrv.dump and add the neccessary table)

- 2.1.7
  - MySQL logging support implemented. Ugly code, but it
    seems to work. Thanks to nucflash for implementing it.
  - 2.1.6 seemed to be crash-proof. Let's hope this one too.

- 2.1.6
  - some more segf_indicator points
  - some segfault problems seem to have disappeared in
    2.1.5. Maybe they were caused by the (wrong) usage of
	'long long' data types?
  - security fix: in 2.1.5 unauthenticated clients were
    able to cause the dialing of lines...

- 2.1.5
  - Shutdown should work now even if user accounting is
    disabled. In that case clients get verified with the
    limit_shutdown_* features (ip-lists).
  - pid_file in the complete-syntax example wasn't correct.
    pidfile is the recognized keyword.
  - heavy changes in configure.in... should be easier
    to use now.
  - kbyte counting replaced with byte counting. Should
    work for upto 4GB, limitation is linux as it's only
	using 32bit unsigned counters

- 2.1.3
  Protocol change to LCP 3.3, minimum required for
  clients is LCP 3.3
  Clients can now request throughput information of
  all lines by using the CMD3_GETALL / UNGETALL
  commands. Furthermore I tried to make some overflow
  fixes in the upload/download counters
  Keywords line_baud_up / down added (specify upload
  + download speed in kbit/s, get's reported to the
  clients).

- 2.1.0
Multiple line support. I had to make a little
protocol change. So wlc 1.1.x doesn't work
anymore. You need at least 1.2.0. The logfile
format changed also a bit. Get the newest lclog
from this server tarball.
Furthermore there's a config file change. You
have to specify the "line" keyword. For further
(bad) description have a look at the file
./config/complete_syntax/linesrv.conf


- 2.0.1
Don't use any WLC version below 1.1.1 with
linesrv version 2.0.1 and later. We've made
some changes in the protocol (LCP3: info_isdn).
