upgrade unlang from 2.1.12 to 3.0.14

[Alan DeKok]

On Jul 6, 2017, at 4:04 AM, adrian.p.smith at bt.com wrote:
> 
> Thanks for all the input, that has cleared up most of my migration issues.

  Good to hear.

> There is one final one however!
> 
> In our old server, for some business logic reasons we artificially create some accounting packets from access requests by writing them into a detail file using the sql_log module to format the request:
> 
> Post-Auth = "%t\n\tAcct-Status-Type = Interim-Update\n\tUser-Name = \"%{User-Name}\"\n\tAcct-Session-Id = \"REJECT\"\n\tBTOpenzone-Reject-Message = \"8021xReject:%{reply:Reply-Message}\"\n\tNAS-IP-Address = %{NAS-IP-Address}\n\tFramed-IP-Address = %{Framed-IP-Address}\n\tCalled-Station-Id = %{Called-Station-Id}\n\tCalling-Station-Id = %{Calling-Station-Id}\n\tAcct-Delay-Time = 0\n\tTimestamp = %l\n"
> 
> This then gets picked up by another server "listening" to the file.
> 
> With the latest code I cannot get either rlm_sql_null or linelog to honour the control characters to allow creation of the pseudo detail file.

  Use the real detail module.

  We've made version 3 be more careful about what it accepts, and what it produces.  In this case, you can't fake out a multi-line message with a module designed to produce single-line messages.

  Alan DeKok.