Control And Monitor Client INSTALLATION NOTES

Contents

1  Import Changes

2  Software Packages Used by Control And Monitor Client

2.1  Building of 3rd party packages

The pkgbuilder building tool is now employed to greatly simplify the installation of third party packages. The environment variable LDASTOPSRCDIR must be set to use the rules given below. The value of this environment variable should be set to the fully qualified path of the top level directory of the LDAS source tree.
Before any of the packages can be installed, a directory of "/ldcg" must be created with read/write permissions for the user installing the software and read permissions for all other users. Although this directory is anchored at the root directory, it can reside anywhere there is sufficient space and have a symbolic link from there to "/ldcg." This needs to be added to the PATH and LD_LIBRARY_PATH environment variables. To set this variable for bourne shell and its derivitives use "PATH=/ldcg/bin:${PATH}; export PATH". For C shell and its derivities use "setenv PATH /ldcg/bin:${PATH}". Also for C shell and derivitives the rehash command will be need to be executed after each package installation. To set this variable for bourne shell and its derivitives use "LD_LIBRARY_PATH=/ldcg/lib:${LD_LIBRARY_PATH}; export LD_LIBRARY_PATH". For C shell and its derivities use "setenv LD_LIBRARY_PATH /ldcg/lib:${LD_LIBRARY_PATH}".
It is required to use stow. Please review the section dedicated to stow and install this package first.
The table below describes which packages are are needed for various configurations of LDAS. The columns "Solaris 10" and "CentOS 5.2/Intel" describe the operating system on which the LDAS software is to be compiled and run. The sub-column CVS stands for building of the LDAS system from the source in the CVS archive. The sub-column Tar-Ball stands for building of the LDAS system from a tar-ball distribution (ldas-x.x.x.tar.gz). The three field values are "Required", "Optional", and "RPM". A field value of "Required" means the package must be built. A field value of "Optional" means the package does not need to be built. A field value of "RPM" means that the package is required and can either be built from its sources or the RPM from RedHat may be used.
Software Packages used by Control And Monitor Client
Package OS Distribution Requiremnts
stow 1.3.3 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
pkgbuilder 0.11.0 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
binutils Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
gcc Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
make 3.79.1 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
m4 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
autoconf Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
automake Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
libtool Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
tcl Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
tk Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
BWidget Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required
BLT Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.2  stow 1.3.3

2.2.1  Description

GNU Stow is a program for managing the installation of software packages, keeping them separate (/usr/local/stow/emacs vs. /usr/local/stow/perl, for example) while making them appear to be installed in the same place (/usr/local). Stow is a Perl script which should run correctly under Perl 5.005 and above. You must install Perl before running Stow. Stow was inspired by Carnegie Mellon's Depot program, but is substantially simpler.

2.2.2  Links

Link DescriptionLink
Home Page
http://www.gnu.org/software/stow/
Download
ftp://ftp.gnu.org/gnu//stow/stow-1.3.3.tar.gz
Mirror
LDAS Patch

2.2.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
stow 1.3.3 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.2.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:stow

2.3  pkgbuilder 0.11.0

2.3.1  Description

Pkgbuilder is a utility designed to automate the process of building third party packages.

2.3.2  Links

Link DescriptionLink
Home Page
http://ldas-sw.ligo.caltech.edu/packages/pkgbuilder-0.11.0.tar.gz
Download
http://ldas-sw.ligo.caltech.edu/packages/pkgbuilder-0.11.0.tar.gz
Mirror
LDAS Patch

2.3.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
pkgbuilder 0.11.0 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.3.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

./configure -prefix=/ldcg
make bootstrap

2.4  binutils

2.4.1  Description

GNU binutils work mostly behind the scenes of Linux development, largely because GNU make and the GCC frontend does so many things automatically. Utilities include: ld as nm objdump objcopy nm ar ranlib strip c++filt size addr2line and dlltool.

2.4.2  Links

Link DescriptionLink
Home Page
http://sources.redhat.com/binutils/
Download
ftp://ftp.gnu.org/gnu//binutils/binutils-.tar.gz
Mirror
LDAS Patch

2.4.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
binutils Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.4.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:binutils

2.5  gcc

2.5.1  Description

The GNU Compiler Collection contains frontends for C, C++, Objective-C, Fortran, Java, and Ada as well as libraries for these languages. It is a full-featured ANSI C compiler with support for K&R C as well. GCC provides many levels of source code error checking traditionally provided by other tools (such as lint), produces debugging information, and can perform many different optimizations to the resulting object code.

2.5.2  Links

Link DescriptionLink
Home Page
http://gcc.gnu.org
Download
ftp://gcc.gnu.org/pub/gcc/releases/gcc-/gcc-.tar.bz2
Mirror
ftp://ftp.gnu.org/gnu//gcc/gcc-/gcc-.tar.bz2
LDAS Patch

2.5.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
gcc Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.5.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:gcc

2.6  make 3.79.1

2.6.1  Description

GNU Make examines the timestamps on a set of interdependent files, and, if necessary, issues commands to bring them up-to-date. The user creates a makefile describing the files, their relationships, and the commands to run. Most often make is used to rebuild libraries and programs when their sources are changed, but it can be used for any situation where one set of files needs to be generated from another set.

2.6.2  Links

Link DescriptionLink
Home Page
http://www.gnu.org/software/make/make.html
Download
ftp://ftp.gnu.org/gnu//make/make-3.79.1.tar.gz
Mirror
LDAS Patch

2.6.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
make 3.79.1 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.6.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:make

2.7  m4

2.7.1  Description

GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible, although it has some extensions (for example, handling more than 9 positional parameters to macros). GNU m4 also has built-in functions for including files, running shell commands, doing arithmetic, etc.

2.7.2  Links

Link DescriptionLink
Home Page
http://www.seindal.dk/rene/gnu/
Download
ftp://ftp.gnu.org/gnu//m4/m4-.tar.bz2
Mirror
LDAS Patch

2.7.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
m4 Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.7.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:m4

2.8  autoconf

2.8.1  Description

Autoconf is an extensible package of m4 macros that produce shell scripts to automatically configure software source code packages. These scripts can adapt the package to many kinds of UNIX-like systems without manual user intervention.

2.8.2  Links

Link DescriptionLink
Home Page
http://www.gnu.org/software/autoconf/
Download
ftp://ftp.gnu.org/gnu//autoconf/autoconf-.tar.bz2
Mirror
LDAS Patch

2.8.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
autoconf Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.8.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:autoconf

2.9  automake

2.9.1  Description

Automake is a tool for automatically generating Makefiles compliant with the GNU Coding Standards. It was inspired by the 4.4BSD make and include files, but aims to be portable and to conform to the GNU standards for Makefile variables and targets. Automake is a Perl script. The input files are called Makefile.am. The output files are called Makefile.in; They are intended for use with Autoconf. Automake requires certain things to be done in your configure.in. This package also includes the äclocal" program. aclocal is a program to generate an 'aclocal.m4' based on the contents of 'configure.in'. It is useful as an extensible, maintainable mechanism for augmenting autoconf.

2.9.2  Links

Link DescriptionLink
Home Page
http://www.gnu.org/software/automake/automake.html
Download
ftp://ftp.gnu.org/gnu//automake/automake-.tar.bz2
Mirror
LDAS Patch

2.9.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
automake Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.9.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:automake

2.10  libtool

2.10.1  Description

GNU libtool is a generic library support script. Libtool hides the complexity of using shared and static libraries behind a consistent, portable interface. Libtool supports building static libraries on all platforms.

2.10.2  Links

Link DescriptionLink
Home Page
http://www.gnu.org/software/libtool/
Download
ftp://ftp.gnu.org/gnu//libtool/libtool-.tar.gz
Mirror
LDAS Patch

2.10.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
libtool Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.10.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:libtool

2.11  tcl

2.11.1  Description

Tcl provides a portable scripting environment for Unix, Windows, and Macintosh that supports string processing and pattern matching, native file system access, shell-like control over other programs, TCP/IP networking, timers, and event-driven I/O. Tcl has traditional programming constructs like variables, loops, procedures, namespaces, error handling, script packages, and dynamic loading of DLLs.

2.11.2  Links

Link DescriptionLink
Home Page
http://tcl.activestate.com/
Download
http://easynews.dl.sourceforge.net/sourceforge/tcl/tcl-src.tar.gz
Mirror
ftp://tcl.activestate.com/pub/tcl/tcl8_3/tcl-src.tar.gz
LDAS Patch

2.11.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
tcl Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.11.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:tcl

2.12  tk

2.12.1  Description

Tk provides portable GUIs on UNIX, Windows, and Macintosh. A powerful widget set and the concise scripting interface to Tk make it a breeze to develop sophisticated user interfaces.

2.12.2  Links

Link DescriptionLink
Home Page
http://tcl.activestate.com/
Download
ftp://tcl.activestate.com/pub/tcl/tcl8_3/tk-src.tar.gz
Mirror
http://easynews.dl.sourceforge.net/sourceforge/tcl/tk-src.tar.gz
LDAS Patch

2.12.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
tk Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.12.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:tk

2.13  BWidget

2.13.1  Description

The BWidget Toolkit is a high-level widget set for Tcl/Tk that uses native Tcl/Tk 8.x namespaces. They feature a professional look and feel and don't require a compiled extension library.

2.13.2  Links

Link DescriptionLink
Home Page
http://tcllib.sourceforge.net/
Download
http://easynews.dl.sourceforge.net/sourceforge/tcllib/BWidget-.tar.gz
Mirror
LDAS Patch

2.13.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
BWidget Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.13.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:BWidget

2.14  BLT

2.14.1  Description

The BLT Toolkit is an extension to Tcl and Tk. It adds new commands and widgets to the Tcl interpreter. Included widgets are 2D graph, barchart, stripchart, tab notebook, and tree viewer.

2.14.2  Links

Link DescriptionLink
Home Page
http://sourceforge.net/projects/blt/
Download
http://easynews.dl.sourceforge.net/sourceforge/blt/BLT.tar.gz
Mirror
LDAS Patch

2.14.3  Build Requirements

Software Package used by Control And Monitor Client
Package OS Distribution Requiremnts
BLT Solaris 10 CVS Required
Tarball Required
CentOS 5.2 CVS Required
Tarball Required

2.14.4  Build Instructions


#
# Please review section 2.1 of this document titled
# "Building of 3rd party packages" on how to correctly
# set the environment variables used here
#

pkgbuilder ${LDASTOPSRCDIR}/doc/utilities/ldas:BLT

3  Installation of the Control And Monitor Client

The Control And Monitor Client software is available only in tarball format. It can be retrieved from http://www.ldas-sw.ligo.caltech.edu//packages/cmonClient-1.16.3.tar.gz. To install the software, use the command "gzip -dc cmonClient-1.16.3.tar.gz - tar xf -". This will create the sub-directory cmonClient-1.16.3.

4  Running the Control And Monitor Client

Change into the subdirectory cmonClient-1.16.3 and execute the command cmonClient. You should see a screen appear on your machine which gives you access to the LDAS system.

5  Reporting problems

Control And Monitor Client uses GNATS for reporting and tracking problem reports. Each major piece of code and each major task has a category. For example, errors that are found in this documentation should be submitted under the category "doc" since it represents a documentation error.

5.1  Accessing GNATS via the Web

https://ldas-sw.ligo.caltech.edu/cgi-bin/gnatsweb.cgi?database=ldas
The above link will bring you to a page explaining levels of severity, levels of priorities, and explain the types of classes. The link at the bottom of the page will bring you into the GNATS system where you will be able to submit and query problem reports.
All users can submit problem and query reports. Only developers can modify problem reports once they have been submitted.

5.1.1  Submitting a new problem report.

Once in the GNATS system, choose "create". This brings up a form which must be filled out.
Does
Don'ts
Once the form has been completely filled out, go to the top or the bottom of the page and select the "submit" button. You will receive e-mail notifying you of your submitted problem report and the id with which it is associate. You will also receive e-mail whenever there is a change to the problem report.

5.1.2  Checking the status of a problem report

There are two ways of checking the status of a problem report. The first is using the "View problem report" option from the GNATs main page. If you have the problem report id, just type in the number and select the "view" button. A page with the full details of the problem report will appear.
The second method allows you to query the GNATS system for problem reports of interest and has two flavors. The simplest is the "Query Problem Reports." Use this method by selecting the "query" button. A web form page will appear. Refine the search by using the drop down selectors and/or using the text widgets. The query is executed after selecting the "submit" button. If you are interested in problem reports that are potentially closed, be sure the "Ignore Closed" button below the "State" field is not selected.
For more advanced queries, select the "advanced query" button. This form allows you to search by time and date and by regular expressions. Again if you are interested in problem reports that are potentially closed, be sure the "Ignore Closed" button in the "State" field is not selected.


File translated from TEX by TTH, version 3.66.
On 4 Nov 2009, 14:00.