18.2.11. TRACE_USERNAME user name Previous topic Parent topic Child topic Next topic

Causes TRACE to only print log messages that result from a RADIUS request from the given User-Name. This is handy for seeing only log messages for a given user when debugging connection problems.
The user name is compared to the User-Name in the incoming request after any RewriteUsername rules have been applied. Setting the TRACE_USERNAME to an empty string (the default) turns off this special behaviour, and all messages that are at or below the current TRACE level will be output.
In the following example, the TRACE level is set to 4, meaning all DEBUG and lower level log messages will be printed. Then the TRACE_USERNAME is set to mikem@open.com.au, which means that only DEBUG and lower log messages due to requests from mikem@open.com.au will be printed. Finally the TRACE_USERNAME is set to an empty string, which means that all DEBUG and lower level log messages will be printed again.
TRACE 4
TRACE_USERNAME mikem@open.com.au
      <<< only messages that are at or below the current TRACE level
      for requests from mikem@open.com.au
      are output here.>>>
TRACE_USERNAME
      <<< no more user-specific logging now. All trace level 4
      messages will be output >>>