The architecture of the future logging systems sounds nice. Are there any pointers on how to integrate my .comp file into the Makefile system? Even examples elsewhere in the source tree would be useful.
On Wed, May 8, 2013 at 4:56 PM, Michael Haberler <mai...@mah.priv.at> wrote: > > Am 08.05.2013 um 17:09 schrieb Curtis Dutton <curtd...@gmail.com>: > > > As far as capturing output, I'll just write any errors encountered to > > stderr. That is perfectly fine as far as I'm concerned. I just had a hard > > time finding out where the linuxcnc logs were located. I couldn't find > them > > in the documentation via search, or in the wiki either. > > It's a good example of one in a long list of cleanups due, as LinuxCNC > sports a, hm, 'organically grown architecture' here ;) > > we currently have: > > in an RT build: > - RT component messages go to the kernel log (printk) > - however messages generated in the motion module, which happen to be > funnelled to milltask, the coordinator, have the potential to wind up on a > UI > - messages by userland HAL components (like you VFD driver) wind up in > stderr which goes to a log file > - a 'message level' applies to all RT components alike, however message > levels for userland components are all one-per-component > > however, in a 'sim' build (and those rules apply to early Xenomai- and > RT-Preempt versions as well) we have: > - RT and userland component messages go to stderr (rt-preempt) and a > xenomai-specific destination (xenomai) > - exceptions for motion as above > > meaning: non-motion messages delivered to UI's: not possible; rest of > them: make sure you know where to dig > > -- > > the code base which should become available later this year addresses this > as follows: > > - there is a single error message queue accessible by all components, > living in a shared memory segment, and independent of RTOS style and > component style > - all messages are tagged by origin and level > - there are two message levels; one for RT components, and one for the > rest of them, to determine disposition > - disposition happens in a demon which receives all messages and may > log/forward as needed - for instance to UI's > > - Michael > > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and > their applications. This 200-page book is written by three acclaimed > leaders in the field. The early access version is available now. > Download your free book today! http://p.sf.net/sfu/neotech_d2d_may > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
