Jon Elson wrote: > Hello, > > I was doing some testing with a fresh checkout from the trunk, > and I had a problem that a bunch of messages in > hal/drivers/hal_ppmc.c did not write messages to the kernel log. > > The lines are of the form : > rtapi_print_msg(RTAPI_MSG_INFO, "something\n"); > > and always used to print out with the .ini file parameter > DEBUG set to at least 1, I think. I tried several numbers here, > including 0x7FFFFFFF, and they still didn't print to the file. > I did get lines from RTAPI_MSG_ERR, but not from INFO. > > Is this possibly a bug, or an intended change in the rtapi behavior?
It's not a change, it has always worked that way. It's also not really a bug, but maybe it is a behavior that could/should be changed. RTAPI is a wrapper API for handling realtime OS stuff, and has no clue about EMC specific things like the DEBUG parameter in the ini file. It has it's own completely independent way of setting debug level - an entry in the /proc file system (/proc/rtapi/debug) determines what level of messages will be printed out. You can do "echo 5 >/proc/rtapi/debug" to force all messages to be printed. (Actually I think 4 will work.) It would not be hard to tweak the EMC run script so that if DEBUG is set at or above a certain value, it would set /proc/rtapi/debug accordingly. Maybe I'll look into that tonight. Regards, John Kasunich ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
