[Asterisk-Dev] Help/hints for debug?

Rich Adamson radamson at routers.com
Fri Dec 24 08:38:32 MST 2004


> > Looking at the wctdm.c code, I see lots of debug statements involving
> > "printk". What is the proper way to turn on debugging for that module?
> > (I've tried changing logger.conf to include debug and starting asterisk
> > with a -d command line switch, but that does nothing for the wctdm module.)
> 
> This is a kernel module, so modifying the Asterisk configuration will 
> not affect it at all.
> 
> If the printk() function is being used, then the output is being sent to 
> the kernel log, and captured by klogd (or whatever equivalent you have 
> on your machine). There may be #ifdef wrappers around the printk() 
> function calls, though, if that is the case you'll need to recompile 
> with the appropriate value defined in the Makefile so that the module 
> will actually generate the log output.

The majority of printk's in wctdm.c are not #ifdef'ed, so I guess the
statements are active in stock compile. Does that sound reasonable?

This happens to be a RHv9 machine. I see klogd is running and the syslog.conf
has the kern.* commented out. Is your best guess simply to uncomment that
line directing output to a file?






More information about the asterisk-dev mailing list