Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  Index 1994  1995  <19961997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: proposal: IOC logger
From: Jeff Hill <johill@lanl.gov>
To: Geng XIAOSONG <gengxs@desy.de>
Cc: tech-talk@aps.anl.gov
Date: Tue, 15 Oct 1996 10:42:18 -0600
Geng XIAOSONG wrote:
> 
> Salut, EPICS folks!
> 
> We have some proposal about IOC logger..
> 

General Comments:

It is true that the original log server is quite primitive and that
it is easy to imagine a number of improvements that could be made to
it. Perhaps the first items on the list should be improvements related
to configuration of a large system incorporating many IOCs.

My main concern is that upgrades are coordinated
so that the improvements at one site do not conflict with
improvements made at other sites. This will minimize the size of
the source code and the time required to train new users.

For example, KECK has recently made changes which allow the log server 
to close the current file and open a new file in a differnt directory
(which is specified by a shell command). Since this proposal provides
a different mechanism by which the directory for the file is specified
I think it reasonable to request that Geng Xiaosong should poll the mail list
to see how many users are using the current mechanism and after
having an E-mail discussion with William Lupton (the author of KECKs
changes - wlupton@keck.hawaii.edu) arrive at a solution that hopefully is 
acceptable to everyone. We could incorporate both mechanisms but perhaps
this would not result in a compact implementation which I think we all 
prefer in the end.


Some specific comments follow:


> Problem background
> ------------------
> 
>   - Seperated log files to record the messages from different IOC's.
>     But, some sites will continue to prefer to keep messages from several
>     IOC's in one file.

This is possible (but possibly inconvenient) today. The (perhaps awkward)
restriction is one log server per file.

> 
>   - Run time reconfiguration of iocLogServer.
> 

Today it is possible to dynamically change the log file directory (but not 
the log file name) via SIGHUP. 

>   Proposal:
>   --------
>   - Use one configuration file to specify all parameters for the server.
> 
>   - One chapter should consist of information where messages from particular
>     must be saved:
> 
>     <IOC name>|          <full path>  |<size limit>|<versioning>|<mail address>
>     ...........................................................................
>     heraVME00 |/.../heraVME00_log.text|1000000     | Y          |claus@desy.de
>     heraVME01 |/.../heraVME00_log.text|1000000     | Y          |claus@desy.de
>     heraVME02 |/.../heraVME02_log.text|4000000     | Y          |csuka@desy.de
>     heraVME03 |/.../heraVME03_log.text|239093      | N          |
>     ...........................................................................
> 
>    * msg from heraVME00 and heraVME01 will be saved in ONE file
> 
>   - To add a new variable "EPICS_IOC_LOG_CONFIG_FILE" which should keep
>     full path to the configuration file.
> 
>   - Send the signal SIGHUP (kill -1 <pid>) to iocLogServer to forse it to
>     read config file again a make inner reconfigurations. (to be discussed)
> 
>     In start time:
> 
>     1. iocLogServer <path to config file>
> 
>     2. If ``config_file'' does not specify in command line then read
>         system env. variable EPICS_IOC_LOG_CONFIG_FILE.
> 
>     3. If env. does not exist, then use today approach.
> 
> Problem background
> ------------------
> 
>    - Once the file is written fully, we need a possibility to inform
>      the system manager about it and stop writing.

I assume that this would occur if "versioning" is "Y" otherwise if
"versioning" is "N" the current behavior of overwriting the oldest
log message would be preserved.

> 
>   Proposal:
>   --------
>    - IOC log sever will check itself whether a new month has started and
>      crate new log file /xx/yy/mm/logfile.

How does this interact with KECK's changes which allow the new directory
to be determined via SIGHUP and the IOC log file command pipe?

> 
>    - Send a mail to the system manager to tell about this.

Should we restrict the mail message rate?


Jeff

-- 
______________________________________________________________________
Jeffrey O. Hill                 Internet        johill@lanl.gov
LANL MS H820                    Voice           505 665 1831
Los Alamos, NM 87545 USA        FAX             505 665 5107


References:
proposal: IOC logger Geng XIAOSONG

Navigate by Date:
Prev: proposal: IOC logger Geng XIAOSONG
Next: Re: proposal: IOC logger watson
Index: 1994  1995  <19961997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: proposal: IOC logger Geng XIAOSONG
Next: Re: proposal: IOC logger watson
Index: 1994  1995  <19961997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·