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  <20082009  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  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: caPutLogging Documentation
From: "Ernest L. Williams Jr." <[email protected]>
To: Steve Lewis <[email protected]>
Cc: [email protected], "Williams Jr., Ernest L." <[email protected]>
Date: Wed, 19 Nov 2008 07:12:28 -0800
Steve Lewis wrote:
Just to clarify:

There are two instances of iocLogServer running.

The first is doing conventional IOC logging. So your st.cmd would have set the environment variables EPICS_IOC_LOG_INET and EPICS_IOC_LOG_PORT and have the line:
iocLogInit()


The second is doing caput logging, using port 7010. So your st.cmd would have:
caPutLogInit("${EPICS_IOC_LOG_INET}:7010")
So this ignores EPICS_IOC_LOG_INET and EPICS_IOC_LOG_PORT?

Hi Steve,
I actually have the caput logging going to the same place as the IOC conventional logging.
That is my recommendation so that I can easily correlate operator changes with possible errors/messages from the IOC. :)
So, I am using:


# =====================================================
# Turn on caPutLogging:
# Log values only on change to the iocLogServer:
caPutLogInit("172.27.8.31:7004")
caPutLogShow(2)
# ======================================================

The above will send messages to my already running iocLogServer.

By the way, the CSS collaboration is working on a messaging system
for EPICS.  I am not sure of the current status.


Thanks, Ernest




Thanks, Steve

[I added techtalk to the CC list. This might be of interest to others.]

On Tuesday 18 November 2008 14:45, Steve Lewis wrote:
 This sounds great, Ernest.  Can you tell me exactly how this fills
 the need?  (I see in subsequent e-mails how you got it to come up.)

 In fact, I have not brought up iocLogServer yet, either.  Can you
 give me a brief sketch of how that is configured?

 At 9:28 PM -0800 2008/11/17, Ernest L. Williams Jr. wrote:
 >I have found that a combination of autosave/restore and caPutLogging
 >will give me the same functionality as the ChannelWatcher:

It is very simple. Set two environment variables
EPICS_IOC_LOG_FILE_NAME=/path/to/logfilename and
EPICS_IOC_LOG_PORT=portnumber and then start iocLogServer (from epics
base). I have attached a small shell script I use to start the log servers
on my local machine.


Cheers
Ben



Replies:
Re: caPutLogging Documentation Benjamin Franksen
Re: caPutLogging Documentation Matthias Clausen
References:
Re: caPutLogging Documentation Benjamin Franksen

Navigate by Date:
Prev: Re: caPutLogging Documentation Benjamin Franksen
Next: CAEN V965 driver Szalata, Zenon M.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: caPutLogging Documentation Benjamin Franksen
Next: Re: caPutLogging Documentation Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  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 ·