Re: iocLogServer simple browser

[Matt Rippa <mrippa@gemini.edu>]

At Gemini we use a Perle CS9000 console server. 
http://www.perle.com/products/CS9000-Console-Server.shtml

It has an NFS log feature which includes timestamps. We couple 
this with an in-house log rotation scheme which works quite well. 
This is completely independent from iocLog.

-Matt


Al Honey wrote:
> 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: tech-talk-bounces@aps.anl.gov
> [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Maren Purves
> Sent: Thursday, November 15, 2007 8:53 AM
> To: 'MacKenzie, Ronald R.'
> Cc: tech-talk@aps.anl.gov
> 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.