EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: C++ logging framework for epics
From: <[email protected]>
To: <[email protected]>, <[email protected]>
Date: Mon, 4 Mar 2013 16:50:30 +0000
Hi Sinisa,

At Diamond we use the conserver application (not Epics specific) to log our IOC output to a file. It also provides a uniform 'console' interface to our soft and VxWorks IOCs. Most of our error/log messages tend to come from Asyn based drivers, and so it's possible to filter which Asyn messages are written on the IOC shell. While we don't use conserver to do any smart filtering (I'm not sure it can do that), it does have the advantage that it captures everything on the IOC shell, including remote console sessions and IOC reboots.

Cheers,
Matt


> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Sinisa Veseli
> Sent: 04 March 2013 14:34
> To: [email protected]
> Subject: C++ logging framework for epics
> 
> Hello,
> 
>  From what I see in the app dev guide, epics base provides few error
> logging facilities that seem to be used by several synapps modules. Are
> there any logging packages targeted for epics that would provide
> something a bit more configurable? Has anyone seen some of the existing
> C++ logging frameworks (log4cxx, log4cplus, boost.log, etc.) used in
> epics applications or IOCs?
> 
> Thanks,
> 
> Sinisa
> 
> --
> Sinisa Veseli
> Software Services Group
> APS Engineering Support Division
> Argonne National Laboratory
> [email protected]
> (630)252-9182


-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 





References:
C++ logging framework for epics Sinisa Veseli

Navigate by Date:
Prev: RE: Recommendations for developing an IOC for PCI Mark Rivers
Next: Re: Installing MEDM on UBUNTU 12.04 Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: C++ logging framework for epics Sinisa Veseli
Next: getBounds Zenon Szalata
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·