Navigation


Changes between Version 2 and Version 3 of Usage


Ignore:
Timestamp:
Mar 3, 2011, 5:02:17 PM (11 years ago)
Author:
Administrator
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Usage

    v2 v3  
    1818
    1919 {{{-f funcname}}} or {{{--dbg_func=funcname}}}::
    20    The debug level will be set to maximum only inside functions with the name ''funcname''. Since this is dynamically evaluated, it works even with static functions and extension functions (that use debug macro from the library), but it is also quite slow. To get detailed information about the handling of incoming messages, you might use for example:
     20   The debug level will be set to maximum only inside functions with the name ''funcname''. Since this is dynamically evaluated, it works even with static functions and extension functions (that use debug macro from the library). It slows the framework execution, so do not use it when not needed. To get detailed information about the handling of incoming messages, you might use for example:
    2121{{{
     22#!sh
    2223$ freeDiameterd --dbg_func=msg_rt_in
    2324}}}
     
    2627   Same as previous one, but all functions from the file ''filename'' will be logged at maximum trace level. Only the basename is compared, ignoring the path, as follow:
    2728{{{
     29#!sh
    2830$ freeDiameterd --dbg_file=app_acct.c
    2931}}}
     
    3133At the moment, all debug messages from the {{{freeDiameter}}} daemon are sent to {{{stdout}}}. If you want to capture them in a file, you should redirect the stream as follow:
    3234{{{
     35#!sh
    3336$ freeDiameterd -dd > ~/fD.log 2>&1
    3437}}}
    3538Or, using the command {{{tee}}}:
    3639{{{
     40#!sh
    3741$ freeDiameterd -dd 2>&1 | tee -i ~/fD.log
    3842}}}