Changes between Version 2 and Version 3 of Usage
- Timestamp:
- Mar 3, 2011, 5:02:17 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Usage
v2 v3 18 18 19 19 {{{-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: 21 21 {{{ 22 #!sh 22 23 $ freeDiameterd --dbg_func=msg_rt_in 23 24 }}} … … 26 27 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: 27 28 {{{ 29 #!sh 28 30 $ freeDiameterd --dbg_file=app_acct.c 29 31 }}} … … 31 33 At 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: 32 34 {{{ 35 #!sh 33 36 $ freeDiameterd -dd > ~/fD.log 2>&1 34 37 }}} 35 38 Or, using the command {{{tee}}}: 36 39 {{{ 40 #!sh 37 41 $ freeDiameterd -dd 2>&1 | tee -i ~/fD.log 38 42 }}}
