...
- Opmantek applications are available for Linux 64-bit systems only.
Redhat/CentOS6, Debian 7, Ubuntu 10 and newer are supported (basically anything running glibc 2.3 and up). - The latest versions of our applications can be found at : https://opmantek.com/network-tools-download/
- You need superuser/root access on the system in question.
- Please note that as of Feb 2017, all Opmantek applications require that
/tmpis mounted with execute permissions (i.e. mounted without thenoexecmount flag).
See below for an alternate procedure if your/tmpis non-executable.
Opmantek Applications Download Formats
...
Please note that the installer needs to run with root privileges, and will terminate with an error message if this requirement is not met.
Alternative procedure if your /tmp should be mounted noexec
As pointed out above, the installer needs do extract the product files into a temporary directory and then restart using the extracted programs.
This fails if the standard temp directory /tmp is mounted with the noexec mount flag.
The simplest workaround is to pick a different location for the temporary directory that is not affected by noexec and tell the installer about it by setting the environment variable TMPDIR.
- Become the superuser with
sudo,su, etc. Pick a suitable directory
root's home directory is likely ok. Runningmountshould confirm - look fornoexec. We recommend that you use an empty new temporary directory for the installer as that simplifies cleanup.Code Block cd; # you're in root's homedir now. or pick some other writable and executable place mkdir installertempTell the installer to use this local temporary directory and start the installation
Code Block export TMPDIR=installertemp # this assumes that opProduct was downloaded/transferred into root's homedirectory; adjust the path accordingly if not. sh ./opProduct-version.runClean up the temporary directory
Code Block rm -rf installertemp unset TMPDIR
Available Installer Options
...