EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: iocLogServer simple browser
From: "Al Honey" <[email protected]>
To: "MacKenzie, Ronald R." <[email protected]>
Cc: [email protected]
Date: Thu, 15 Nov 2007 09:01:10 -1000
Actually the iocLog in and of itself is insufficient as it does not
capture low level operating system panic calls. At Keck, we log the IOC
console output, of course that has no time tags and must be correlated
with the iocLog to determine when events occurred, which is sometimes
tedious.

Several months back there was an e-mail thread on processes that allow
good terminal server/console monitoring and logging. It could be useful
to review that thread.

Cheers,
Al


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Maren Purves
Sent: Thursday, November 15, 2007 8:53 AM
To: 'MacKenzie, Ronald R.'
Cc: [email protected]
Subject: Re: iocLogServer simple browser

Hi Ron,

we log to a new file each day, and if you want to read it you
can use system commands like less, tail, grep, or some combination
of the those (something along the lines of "tail -f <file>| grep
<machine>")

HTH,
Maren

Jeff Hill wrote:
> Hi Ron,
> 
>> Does a simple little program exist in C to read the iocLogServer
>> circular file as messages are written to it?  I'm just wanting to see
>> the circular file messages from the program on the screen (stdout).
> 
> I'm not aware that any program like that exists.
> 
> Perhaps a superior approach would be to modify the log server so that
it
> sends the log messages by default to stdout if the
EPICS_IOC_LOG_FILE_NAME
> environment variable isn't defined (or is empty). I suppose also that
the
> logic in the log server implementing a circular file would need to be
> selectively disabled if the file descriptor being written to isn't a
file
> (we could easily test the file descriptor to see if it is a file or
not).
> 
> There are probably already some UNIX command line tools that pipe
their
> input to a length constrained circular file? And of course the command
line
> tool tee can be used to break out to multiple destinations.



Replies:
Re: iocLogServer simple browser Matt Rippa
References:
RE: iocLogServer simple browser Jeff Hill
Re: iocLogServer simple browser Maren Purves

Navigate by Date:
Prev: Re: iocLogServer simple browser Maren Purves
Next: Re: iocLogServer simple browser Matt Rippa
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: iocLogServer simple browser Maren Purves
Next: Re: iocLogServer simple browser Matt Rippa
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·