On 2013-02-26 16:23, Sebastian Kuzminsky wrote: > On 02/26/2013 01:38 AM, Michael Haberler wrote: >> sim build: >> - there is no /proc/rtapi/debug since sim builds dont sport kernel modules >> and hence no procfs/sysfs entries >> - the program which runs 'sim RT modules', rtapi_app, currently has no way >> of setting the RTAPI message level for the simulated RT components. >> - hence, with userland setting the message level in a usermode component >> does not apply to any 'simulated RT components' either >> - if you want more detailed (level<RTAPI_MSG_ERR) RTAPI error messages from >> an RT component with the userland thread styles, the current method is to >> add a 'rtapi_set_msg_level()' to rtapi_app_main of the component in >> question, and recompile (I would love to be corrected on this wart.) >> - this 'sim build' situation applies to all userland thread styles (xenomai, >> RT-PREEMPT, Posix). RT components happily print to the 'console' (wherever >> that output goes), since it's all usermode now. > > Standard out and standard error of all linuxcnc processes is captured by > the linuxcnc starter script and written to a log file in tmp. The > logfile is given a random name, and removed when linuxcnc exits, both > these behaviors make it harder than it should be to inspect them.
Perhaps doing what the X server does is a considerable (and easy) improvement: place the log file (with a fixed name) in /var/log/ and rewrite it on each startup. -- Arvid ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
