This page contains information about updating and archiving of the AMMA/GAMA library.

When and where is it committed?

The updating has three phases. The first one is currently only run on the solaris architecture. During this phase all of the source files are checked out in order to create a consistent source data set across all architectures in a short time. During the second phase the system tries to make the whole system in the development area and checks the consistency of header files and all libraries. If the making fails during the second phase the whole system stops. If the development area is successfully updated, in the third phase the system makes all objects in the public area. The updating system is started by the cron program using the setting of crontab tables.

Start times and machines of the updating:

The documentation generation is standalone process because it takes rather long time.

Start times and machines of documentation generation:

The log files of the last update of AMMA/GAMA library

This section contains information about the results of updating of the AMMA/GAMA library.

AMMA/GAMA Archiving

All RCS subdirectories are copied every night on the different hard disk than the whole cpug partition is located on. Currently the /vol/vssp/avisdata partition at kili is used. The archiving script is started on kili by the cron program using the following setting of the crontab table:
50 02 * * * /bin/sh /vol/vssp/cpug/amma/tools/archive/doArchive
The log file from the last archiving session can be found here .
R.Marik@ee.surrey.ac.uk