Linelog & radmin

[Peter Balsianok]

Well, i need to have the content of REQUEST,CONTROL & REPLY for solving
customer trouble tickets. I want to have it on the same place as main log.
I see benefit to have HUPing in the rad_linelog (e.g.  log rotation). At
this moment i have only one options, after log rotation i have to restart
whole server.

Linelog configuration:

linelog log_request {

  filename = ${log.file}

  format = "%t : Info: REQUEST(%{User-Name}): %{pairs:request:}"

}


linelog log_control {

  filename = ${log.file}

  format = "%t : Info: CONTROL(%{User-Name}): %{pairs:control:}"

}


linelog log_proxy_request {

  filename = ${log.file}

  format = "%t : Info: PROXY-REQUEST(%{User-Name}): %{pairs:proxy-request:}"

}


linelog log_reply {

  filename = ${log.file}

  format = "%t : Info REPLY(%{User-Name}): %{pairs:reply:}"

}


linelog log_proxy_reply {

  filename = ${log.file}

  format = "%t : Info PROXY-REPLY(%{User-Name}):
Packet-Type=%{proxy-reply:Packet-Type} %{pairs:proxy-reply:}"

}

On Mon, Oct 17, 2016 at 5:36 PM, Alan DeKok <aland at deployingradius.com>
wrote:

> On Oct 17, 2016, at 4:29 AM, Peter Balsianok <balsianok.peter at gmail.com>
> wrote:
> >
> > Hi,
> >
> > When i use radmin ... -e 'hup main.log', linelog (log_request,
> log_control
> > & log_reply) will not write information into main.log. Why ?
>
>   linelog doesn't write messages to the main log.  You can configure it to
> write to the same *filename*.  But that's different.
>
>   And if you HUP the main log, you didn't HUP linelog, and so it doesn't
> change.
>
>   Perhaps you could explain how you've configured linelog, and why you
> expect that HUPing the main log will also cause linelog to get HUP'd, too.
>
>   Alan DeKok.
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/
> list/users.html