4.
HOW TO MAINTAIN BEAMS
The user ‘beams’ owns all the beams-applications. The reason for this is that the ‘root’-
user is not required for updating beams. Thus when the beams applications has to be
upgraded, the ‘beams’-user has to be used.
4.1.
Beams-script
A beams-
script “beams” exists in the home-directory of user “beams”. With this script the
releases of beams can be maintained. This includes: downloading new beams releases,
installing/extracting releases and even downgrading.
Go to the “beams”-directory:
[beams@a217 ~]$ cd ~
In this directory the script “beams” can be executed:
[beams@a217 ~]$ beams
Usage:
beams <version> [-ghixs]
Type "beams --help" for detailed help.
As the bottom line says, type “
beams --help
”.
Read this detailed help carefully.
4.2.
Upgrading beams
The usual action to start with an upgrade of “beams” is first looking for available releases
and what is installed on the system. The option “
--show
” does this all:
[beams@a217 ~]$ beams --show
Usually the last beams-release is the best beams-
release. When a new “beams”-release
is available, e.g. “y09_07a”, install/upgrade it next to the other releases as follows:
[beams@a217 ~]$ beams y09_07a --get --install
Although a new beams-release can be got and installed in one action as shown above, it
is recommended to do it in two steps.
First get the release y09_07a from the Vistec ftp server:
[beams@a217 ~]$ beams y09_07a --get
Then extract and install beams-release y09_07a:
[beams@a217 ~]$ beams y09_07a --install
That is all to upgrade beams.