Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Wed, 18 Apr 2012 15:06:34 -0500

Hi Matt,

On 2012-04-18 [email protected] wrote:
> 
> The problem is is that we already have loads of drivers issuing messages
>  that they shouldn't do, so it would be good to have a solution that
>  doesn't involve modifying these. True, lots of the messages should be only
>  printed once. But there is a case for a driver repeating some kinds of
>  message at some slow rate, to inform the terminal that 'something is still
>  not right'. This gets round the problem of a single message being lost due
>  to some other printout going on.

Is the fundamental issue then that its hard to use the IOC console to debug or 
fix problems because of the volume of error messages you're getting?  That's 
what 'eltc 0' is for, it stops all the background error messages coming from 
Asyn perfectly for me.

Now if you can't use that because the IOC doesn't also send its errors to an 
iocLogServer and using 'eltc 0' would cause them to be lost completely, you 
could create an errlog listener which buffers (and possibly de-duplicates if 
you wish) the errlog messages into RAM.  You would provide your own command 
which turns on the buffer and calls eltc(0), and another one which prints out 
the stored messages, stops buffering and calls eltc(1) for when you're 
finished debugging.  See errlog.h and chapter 10 of the AppDevGuide for more 
details of the errlogAddListener() API.

HTH,

- Andrew
-- 
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System