Experimental Physics and
Industrial Control System

"Jeff Hill" <[email protected]> · Mon, 18 Jul 2005 10:37:28 -0600

> 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

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System