Difference between revisions of "Seon update"

Revision as of 21:35, 12 November 2007

Requirements

If you have a software support bought with your software distribution, you may receive updates from time to time via several media. These media can be:

• Download links in the internet
• Files via OFTP, received via
  • ISDN
  • ENX
  • Internet
  • etc.

Run update automatically

These update files, if received via OFTP, have always the virtual filename

Seon_UPDATE

When this flag is set, your Seon installation tries to check the integrity and signature of this package internally. For this purpose, an event binary is (configured here) started. This event binary (default:

/opt/seon/bin/seonupdate

is started with the parameter "-f". It checks the signature of the file and if valid, it extracts the update procedure program and executes it in an Seon shell. The update process searches for the Seon environment variables and uses them to change and update the installation.

Run update semi-automatically (1)

If you have received such a signed update file manually or houy ave disabled this feature, you are able to re-start the event program manually. For this (in a standard environment), call the update program with appropriate parameters. They are documented here.

Example:

/opt/seon/bin/seonupdate -f /tmp/Seon_UPDATE

Run update semi-automatically (2)

You may have received a file which is a verified and extracted version of the "Seon_UPDATE" file. They have normally a file extension of ".sh". This file is a complete Seon installation package, which checks if it's running inside Seon. In order to do this manually, use the Seon shell "shox".

Example:

/opt/seon/bin/shox -e /tmp/seon_update_linux_x86_he.sh