> From: email@example.com
> To: firstname.lastname@example.org
> Subject: Re: SEQ with dynamic assignment of PV in array variable
> Date: Tue, 4 Jun 2013 14:45:02 +0200
> The second reason is that the standard EPICS errlog facility can be used to
> much the same effect (and note that it uses a much saner locking policy), i.e.
> a simple wrapper around errlogPrintf, perhaps using a CPP macro to add the
> state set and/or program name to the message.
#define PRINTF errlogPrintf
> Admittedly, you cannot log
> different program instances into different files, but if you incorporate a
> suitably unique string into the messages then filtering them out of the IOC-
> wide log file can be done easily with standard unix command line tools such as
Are you talking about redirection like
Then the 'logfile' parameter provided to the seq is obviously ignored.
The only issue I have with this is that it is all or nothing.
Admittedly, with the SEQ I can use grep when errlogs are redirected to a file.
BUT I am not so sure I can do this with other application (stream ,etc)
But when there is no redirection, my IOC terminal is flooded with potentially irrelevant messages.
As anyone found a smart/easy way to filter/redirect messages based on the message source (asyn, stream, seq, autosave, etc) ?