EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: iocLogServer change?
From: "Allison, Stephanie" <[email protected]>
To: "Jeff Hill" <[email protected]>
Cc: <[email protected]>
Date: Mon, 18 Jul 2005 10:07:23 -0700
Hi Jeff,

Yes - we'll do something similar to the way ALH is compiled (with or without CMLOG).

When we test, we'll test both ways.  

Stephanie

-----Original Message-----
From: Jeff Hill [mailto:[email protected]] 
Sent: Monday, July 18, 2005 9:37 AM
To: Allison, Stephanie
Cc: [email protected]
Subject: RE: iocLogServer change?


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

OK with me. 

Of course, given that the log server's best feature is its simplicity, it wouldn't be great if the log server only built, or ran, if cmlog was installed, but I doubt that this is your intention. You will no-doubt make this a compile and or run time option?

Jeff

> -----Original Message-----
> From: Allison, Stephanie [mailto:[email protected]]
> Sent: Wednesday, July 13, 2005 2:03 PM
> To: EPICS tech-talk
> Subject: iocLogServer change?
> 
> 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



Navigate by Date:
Prev: RE: iocLogServer change? Jeff Hill
Next: RE: errlogXXX functions and behavior Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: iocLogServer change? Liyu, Andrei
Next: ca gateway configuration for subnets Chris Timossi
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·