The basic command to install an RPM package is rpm -i <package_file>. Although RPM, by design, does not support configuration during installation (with the Linux recommended approach being to configure after installation) - the 1E Client does in fact support configuration through the use of environment variables. These can be easily set in a bash command line by one or more space-separated name=value pairs preceding the install command. So, if the RPM package file name is 1e.client-RHEL_7.1_x64_v4v184.108.40.20645.rpm and the Tachyon Server (assuming that the switch and the background channel are both installed on the Tachyon Server) has the DNS Name FQDN tachyon.acme.local then the command to run would be:
sudo SWITCH=tachyon.acme.local:4000 BACKGROUNDCHANNELURL=https://tachyon.acme.local:443/Background/ rpm -i 1e.client-RHEL_7.1_x64_v4v220.127.116.113745.rpm
Please refer to 1E Client configuration settings and installer properties for a list of other configuration properties that can be configured in the same way.
|The correct case for each property must be used when entering the Linux installer command.|
When the package starts to install you may notice that the ldconfig command generates a warning saying that a .py file is not an ELF file - it has the wrong magic bytes at the start.
This is because ldconfig assumes all files in /usr/lib are ELF files, and that file is a python file.
You can safely ignore this warning.
After the package is installed the application configuration files will be installed to the following directory:
After running the Linux RPM package the client is installed and started as a daemon (service).
The client certificate Tachyon.pfx and a cacert.pem file are required in the hidden directory: /etc/1E/Client/.sslcerts
If Tachyon.pfx contains the same certificate trust chain as the Tachyon Switch, then cacert.pem is optional. This is because the client will have already cached the public certificates when it parses Tachyon.pfx and cacert.pem will be duplicating the public certificate information. If Tachyon.pfx is using a different certificate trust chain from the Tachyon Switch, then cacert.pem is always required.
Please refer to 1E Client command-line parameters if you would like to see details of other CLI commands.
This method is suitable for reconfiguring all 1E Client settings on non-Windows devices because only Tachyon client features are available and all settings are stored in the 1E Client configuration file.
Each client device requires its own certificate, which must be created as a .pfx file.
Using OpenSSL to create the .pfx file
Storing the .pfx on the client
The following command-line can be used to uninstall the 1E Client on Linux:
Uninstallation will leave behind files, folders and registry entries that were created after installation: