Experimental Physics and Industrial Control System
Hi All,
We're looking at upgrading iocLogServer so that it either writes messages to a file, like it does now, or forwards the messages to the cmlogServer (which would make iocLogServer be a cmlog client). We think it's easier to do this than to port the CMLOG client and daemon, and particularly ACE, to our RTEMS IOCs. Part of this effort would also be to add support for messages that contain both ASCII text and other ASCII "tags" like facility, status, severity, and task name.
Any comments? Dumb idea? Anybody interested in something like this? Should it be done in such a way that it can go into some future EPICS base version with the new features enabled via some configure file? Or left unbundled?
Thanks,
Stephanie Allison
SLAC/SSRL, SLAC/LCLS
- Replies:
- Re: iocLogServer change? Steven Hartman
- Re: iocLogServer change? Matthias Clausen
- RE: iocLogServer change? Jeff Hill
- Re: iocLogServer change? Carl Cork
- Navigate by Date:
- Prev:
RE: errlogXXX functions and behavior Ernest L. Williams Jr.
- Next:
Re: iocLogServer change? Steven Hartman
- 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
- Navigate by Thread:
- Prev:
RE: errlogXXX functions and behavior Ernest L. Williams Jr.
- Next:
Re: iocLogServer change? Steven Hartman
- 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