Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated info re -y mode

...

Please note that the installer needs to run with root privileges, and will terminate with an error message if this requirement is not met.

Available Installer Options

You can see an overview of the available options related  to the self-extracting aspect when you start a run

...

file with --help

...

:

  • --keep ensures the unpacked data left behind (in the opProduct-version directory) after the interactive installer component has finished.
  • --noexec causes no interactive installer component to be run.(

The combination of --noexec and --keep provides the equivalent of unpacking the tar files provided with earlier releases.

...

 

You can also pass options to the interactive installer component, but these must follow after a "--" delimiting argument

...

:

  • If you want to perform a simulation run of the installation, use the -n option - : the installer will only print what it would do, what files it would copy and so on, but will not perform any of these steps.
  • By default the installer is interactive and will prompt you for decisions and confirmations; If you want to run it in automatic non-interactive batch mode, use the -y option.
    In this case all dialogs and prompts are automatically answered 'y'.
  • If you wanted want to install the product into a non-standard directory, you can pass the argument -t <targetdir> to the installer component.
    Please note that you will have to adjust a number of configuration files in this case.
  • It is possible to generate more detailed diagnostic output in the installer log file, using the -d option.

 

For example, sh ./opFlow-3.0.5.run --keep -- -n would start the installer in simulation mode (-n) and leave the unpacked files behind (--keep) when done.

Logs and Backups

The installer saves a log of all actions taken, files copied etc. in the installation directory as install.log, ie. normally it'll be in /usr/local/omk/install.log. Subsequent upgrades or installations of other Opmantek products will add to that logfile, so you may very well want to remove or clear the install.log file before upgrading or adding extra software.

...