InterMapper for Red Hat Linux is packaged as a RPM file, which contains the necessary programs and support files. To install InterMapper from the RPM file, you will use the rpm -ivh "location" command. To query if InterMapper is already installed, type rpm -q InterMapper. To remove InterMapper from your system after installing it, type rpm -e InterMapper.
Most modern versions of RedHat have the capacity to check a gpg signature on packages being installed. This allows you to verify the integrity of the downloaded file. To install the Dartware gpg public key, run the following commands:
$ curl -O http://download.dartware.com/debian/dartware_public_key.asc
$ /bin/su -
# rpm --import <path_where_public_key_was_saved>/dartware_public_key.asc
Once you have imported this key, rpm will remember it for future releases and you will not need to import it again.
If you wish to check the signature on the InterMapper package before installing it, you may do so as follows:
$ rpm -K "InterMapper-4.6.9-1.i386.4x.rpm"
If the package signature is correct, you will see this output:
InterMapper-4.6.9-1.i386.4x.rpm: (sha1) dsa sha1 md5 gpg OK
The following directions will install InterMapper from the RPM.
$ /bin/su -
# cd <directory-containing-rpm>
# rpm -ivh "InterMapper-4.6.9-1.i386.4x.rpm"
Installing the RPM automatically creates a system user named intermapper, starts the server, and configures it to run automatically on startup. The default configuration will save InterMapper's files in the /var/local/InterMapper_Settings/ directory.
Launch InterMapper Console from the Gnome menu (under Applications > System Tools > InterMapper) or the KDE menu (under K > System > InterMapper), or type:
$ /usr/local/bin/intermapper
To upgrade your InterMapper installation to a newer version, you will "erase and re-install". Your InterMapper settings directory, which includes all of your maps, logs, and notification settings, is not removed when you un-install using "rpm -e". Although you will not lose any data during the re-installation, this might still be a good time to make a backup of the InterMapper settings folder.
$ /bin/su -
# cd <directory-containing-rpm>
# cp /usr/local/etc/intermapperd.conf /tmp/intermapperd.conf
# rpm -e "InterMapper"
# rpm -ivh "InterMapper-4.6.9-1.i386.4x.rpm"
# mv -f /tmp/intermapperd.conf /usr/local/etc/intermapperd.conf
# /etc/init.d/intermapperd restart
To remove InterMapper Server, you will use the "rpm -e" command. The "rpm -e" command will not remove any files created by InterMapper, such as those stored in your "InterMapper_Settings" directory.
$ /bin/su -
# rpm -e "InterMapper"
To completely remove all remnants of the software, you must also locate and remove the "InterMapper_Settings" directory, as well as the intermapper user. This will remove all of your maps and chart data, as well, so be sure you have backed them up appropriately if necessary prior to removing the "InterMapper_Settings" directory.
$ /bin/su -
# rm -rf <Path to InterMapper_Settings Directory>
# /usr/sbin/userdel intermapper
To manually stop the server, type:
$ /bin/su -
# /etc/init.d/intermapperd stop
To manually start the server, type:
$ /bin/su -
# /etc/init.d/intermapperd start
If the server started successfully, you will see the OK message:
Starting intermapperd: [ OK ]
There are a few things you may change about the way the InterMapper server runs by editing the configuration file "/usr/local/etc/intermapperd.conf". The more common settings are discussed here, but all of them are documented by comments inside that file.
You may change the location where InterMapper stores your maps, charts and probes. This directory must be writable by the user that the InterMapper server runs as.
SettingsFolder "/path/to/InterMapper_Settings"
You may set the user and group that InterMapper runs as; the user and group must exist already. Don't forget that you'll need to change the ownership of the SettingsFolder to match:
User "newuser"
Group "newgroup"
$/bin/su -
# /etc/init.d/intermapperd stop
# chown -R newuser:newgroup /path/to/InterMapper_Settings
# /etc/init.d/intermapperd start
If you do not have a window system on your server machine, you must use "InterMapper RemoteAccess" to administer the InterMapper Server from another computer over the network. Before the server will accept connections from InterMapper RemoteAccess, you must launch the server with a command-line argument telling it where you will connect from. Type the following commands to stop the InterMapper Server, then restart it manually using the -A option:
$ /bin/su -
# /etc/init.d/intermapperd stop
# /usr/local/bin/intermapperd -f /usr/local/etc/intermapperd.conf -A "remote:password@*.*.*.*"
The InterMapper server will now accept Administrator connections from any IP address (*.*.*.*) with the user ID "remote" and the password "password". You should immediately launch InterMapper RemoteAccess on another computer and login to this new InterMapper system to set up your InterMapper users and groups.
There is a bug when using Java with Compiz or certain other window managers that affects InterMapper, resulting in blank windows when starting either the InterMapper console or InterMapper RemoteAccess. This bug has been mitigated somewhat by Java 6 Update 1, but problems still remain. As a work-around, you can set the AWT_TOOLKIT environment variable to "MToolkit" prior to starting the InterMapper GUI. This tells Java to revert to an older rendering method, which will not integrate as well with modern desktop environments, but doesn't suffer from the same bug.
$ AWT_TOOLKIT=MToolkit /usr/local/bin/intermapper
If you wish to set this option for future sessions, you'll need to add that variable to ~/.bashrc:
$ echo -e "\nexport AWT_TOOLKIT=MToolkit" >> ~/.bashrc
Any new terminal windows that you open will have this setting in them by default as soon as you have run this command, but applications started from the menu will not pick it up until after you log out and log back in again. This will work for all Java applications on your system (which were probably similarly broken), not just InterMapper.