Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Tue, 17 Apr 2012 15:26:49 +0000

You can also turn off asynTrace messages for a particular device with

asynSetTraceMask(port, addr, 0)

But I see the utility of what Matt is proposing.  We use procServ to run our IOCs, both soft IOCs and vxWorks IOCs.  On vxWorks the procServ is controlling a telnet session to an Ethernet terminal server, which is connected to the vxWorks console port.  For logging we just use the log file capability of procServ, not a special logging program.  If a device becomes unavailable the log file can quickly grow very large with asynTrace error messages.

Of course we could manually set the asynTrace mask to 0, as shown above.  But it would be nice to have the capability that Matt proposes, to automatically reduce the number of messages in the log file if they are all just repeats.

Mark

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Johnson
Sent: Tuesday, April 17, 2012 10:01 AM
To: [email protected]
Subject: Re: log message filter in Asyn

Hi Matthew,

On 2012-04-17 [email protected] wrote:
> Is there any interest in having a log message filter down in the Asyn
> layer?

Just making sure you know that you can turn off console error log message 
output if you want to: The IOC command 'eltc 0' disables all errlogPrintf() 
output on the console, and 'eltc 1' turns it back on again. The acronym stands 
for Errors Logged To Console; it does not stop messages being sent to the 
iocLogServer.  If you're trying to stem a fire-hose of error messages while 
debugging this is usually all you need.

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