Experimental Physics and
Industrial Control System

Eric Norum <[email protected]> · Tue, 17 Apr 2012 08:39:45 -0700

On Apr 17, 2012, at 8:26 AM, Mark Rivers wrote:

> 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.

Agreed, but I'm holding to my opinion that this capability belongs in the log server, not in all the log clients.   It certainly does not belong in the ASYN layer.   In the errlogPrintf layer, perhaps, but really this belongs in the log server.

-- 
Eric Norum
[email protected]

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System