debug log and syslog

[tnt at kalik.net]

>I can run debug log by starting radiusd -X , but for production, I want
>logs to go to a file and not stdout .

http://linuxbasics.org/course/book/chap_05

>for now with that config I only get 2 lines in radiusd.log when I log in
>802.X EAP-ttls , telling:
>
>Sep  5 10:42:30 radiustux radiusd[14619]: Login OK: [procacci] (from
>client APS_Cisco port 29 cli 00-1F-3C-59-5E-52)
>Sep  5 10:42:30 radiustux radiusd[14619]: Login OK: [anonymous] (from
>client APS_Cisco port 29 cli 00-1F-3C-59-5E-52)
>

What else do you want? You can log additional lines with linelog module.

linelog {

     filename = ... you probably want radius.log file

     format = "Things you want to log ..."

}

If you have attribute values in format statement list linelog in the
section where the values will be known (post-auth etc.).

Ivan Kalik
Kalik Informatika ISP

>for now with that config I only get 2 lines in radiusd.log when I log in
>802.X EAP-ttls , telling:
>
>Sep  5 10:42:30 radiustux radiusd[14619]: Login OK: [procacci] (from
>client APS_Cisco port 29 cli 00-1F-3C-59-5E-52)
>Sep  5 10:42:30 radiustux radiusd[14619]: Login OK: [anonymous] (from
>client APS_Cisco port 29 cli 00-1F-3C-59-5E-52)
>
>with radius -X I get a lot more, can I have at least more than these 2
>lines ?
>thanks .
>
>-
>List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>