1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: seqLog obsolete / errlog filtering based on source |
From: | Mark Rivers <[email protected]> |
To: | "'Emmanuel Mayssat'" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Wed, 5 Jun 2013 19:09:47 +0000 |
All messages generated by asyn can be redirected per asyn port driver, with asynSetTraceFile(port, addr, file).
Mark From: [email protected] [mailto:[email protected]]
On Behalf Of Emmanuel Mayssat > From:
[email protected] > The second reason is that the standard EPICS errlog facility can be used to #define PRINTF errlogPrintf > Admittedly, you cannot log Are you talking about redirection like RunIoc 2>my_log_file ? 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. 1/ 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) 2/ 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) ? -- Emmanuel |