INTERNAL: How To Thoroughly Uninstall IDL Or ENVI From UNIX Systems
Anonym
Uninstalling a given IDL or ENVI installation on a Windows system is a pretty straightforward operation. You highlight your program in a Windows Control Panel dialog box and click on an 'Uninstall' button and pretty much all hidden remnants of the former installation are deleted.
On UNIX there is no corresponding automated uninstaller. The simple rule for uninstallation is: Using " rm -rf" delete the directory tree rooted at 'idl_[version]'. That does not necessarily delete all the files that were installed during the IDL installation. Although the remnants are small in disk space consumption, many users might like to have all files associated with the IDL installation cleaned off their system. This Help Article is designed to help users find the files that were installed outside the 'idl' directory tree, files that can be safely uninstalled after the 'idl' tree has been removed.
Note: This Help Article is not relevant to users who are upgrading ENVI or IDL or installing a different version after removing an old. Those users would have no benefit from uninstalling hidden files; they are already going to be overwritten by the new install of IDL. Such users would only have to run "rm -rf idl_[version]" on the directory tree of the old version they want to remove.
The instructions below are specifically for installations in the default installation path of IDL 6.3 on Red Hat Linux. Even though Red Hat Linux designates its default installation, boot script and web server paths differently than others, users of IDL 6.2 or later for other UNIX-based operating systems should be able to extrapolate from the instructions below to learn how to thoroughly uninstall on their own O.S.'s.
You probably must log in as 'root' or use the " sudo" prefix command to acquire proper permissions to remove the files named below.
STEP 1: Remove symbolic links
If, in any of your Exelis product installs you entered "Yes" to the option "Should we create symbolic links ...?", then use "rm [filename]" to remove the following soft link "files" from your host's '/usr/local/bin/' subdirectory:
For those who have ever installed IDL:
- idl
- idlde
- idldemo
- idlhelp
- ionhelp
- idlman
- ionman
- idlrpc
- rsilicense
... and/or all variations of the above that append an underscore and a version number to the above.
For those who have ever installed ENVI:
- envi
- envi_rt
- envihelp
- envi_tut
- enviman
... and/or all variations of the above that append an underscore and a version number to the above.
For those who have ever installed ION Script and/or ION Java:
- iond
- ionstat
- iondown
... and/or all variations of the above that append an underscore and a version number to the above.
STEP 2: There might also be symbolic directory links named "idl", "ion" and/or "envi" in the RSI Directory, i.e. the parent directory of the 'idl_[version]' tree. Those links will be broken when you in short remove the 'idl_[version]' tree. Remove those links with a simple call to "rm idl", etc.
STEP 3: Uninstall boot scripts for Exelis Visual Information Solutions FLEXlm license management
If, in any of your installations of ENVI and IDL, you answered "Yes" to the option to have boot scripts for license management installed, then you will want to take this step before any other. Look in the '/usr/local/itt/idl_6.3/bin/' directory for a script named 'lmgrd_install'. On a Linux host these are the critical lines in that script:
"Linux")
cp sys5_idl_lmgrd /etc/rc.d/init.d
if [ -f /etc/rc3.d/S99sys5_idl_lmgrd ]; then
rm -f /etc/rc3.d/S99sys5_idl_lmgrd
fi
if [ -f /etc/rc4.d/S99sys5_idl_lmgrd ]; then
rm -f /etc/rc4.d/S99sys5_idl_lmgrd
fi
if [ -f /etc/rc5.d/S99sys5_idl_lmgrd ]; then
rm -f /etc/rc5.d/S99sys5_idl_lmgrd
fi
if [ -f /etc/rc0.d/K01sys5_idl_lmgrd ]; then
rm -f /etc/rc0.d/K01sys5_idl_lmgrd
fi
ln -s /etc/rc.d/init.d/sys5_idl_lmgrd /etc/rc3.d/S99sys5_idl_lmgrd
ln -s /etc/rc.d/init.d/sys5_idl_lmgrd /etc/rc4.d/S99sys5_idl_lmgrd
ln -s /etc/rc.d/init.d/sys5_idl_lmgrd /etc/rc5.d/S99sys5_idl_lmgrd
ln -s /etc/rc.d/init.d/sys5_idl_lmgrd /etc/rc0.d/K01sys5_idl_lmgrd
;;
The "cp ..." line tells you where the hard copy of the boot script went. The "ln ..." lines tell you where the soft links went. If you "rm ..." all five of these items, you will entirely undo the 'lmgrd' boot script installation.
STEP 4: Uninstall boot scripts for DICOM Network Services
If you installed the optional medical application module Dicom Network Services, then you will next want to check the content of your host's '/usr/local/rsi/idl_6.3/bin/dicomexstorscp_install' script. Search for the section that looks like this:
"Linux")
if [ ! -w /etc/rc.d/init.d ]; then
echo "You do not have write permissions to /etc/rc.d/init.d." 1>&2
exit 1
fi
cp $IDL_BIN/sys5_idl_dicomexstorscp /etc/rc.d/init.d
if [ -f /etc/rc3.d/S99sys5_idl_dicomexstorscp ]; then
rm -f /etc/rc3.d/S99sys5_idl_dicomexstorscp
fi
if [ -f /etc/rc4.d/S99sys5_idl_dicomexstorscp ]; then
rm -f /etc/rc4.d/S99sys5_idl_dicomexstorscp
fi
if [ -f /etc/rc5.d/S99sys5_idl_dicomexstorscp ]; then
rm -f /etc/rc5.d/S99sys5_idl_dicomexstorscp
fi
if [ -f /etc/rc0.d/K01sys5_idl_dicomexstorscp ]; then
rm -f /etc/rc0.d/K01sys5_idl_dicomexstorscp
fi
ln -s /etc/rc.d/init.d/sys5_idl_dicomexstorscp /etc/rc3.d/S99sys5_idl_dicomexstorscp
ln -s /etc/rc.d/init.d/sys5_idl_dicomexstorscp /etc/rc4.d/S99sys5_idl_dicomexstorscp
ln -s /etc/rc.d/init.d/sys5_idl_dicomexstorscp /etc/rc5.d/S99sys5_idl_dicomexstorscp
ln -s /etc/rc.d/init.d/sys5_idl_dicomexstorscp /etc/rc0.d/K01sys5_idl_dicomexstorscp
;;
Once again, the "cp ..." line tells you where the hard copy of the boot script went. The "ln ..." lines tell you where the soft links went. If you "rm ..." all five of these items, you will entirely undo Dicom Network Service's boot script installation.
STEP 5: Customers, who have installed ION Script and/or ION Java are very likely to find in their web server's directory tree files that have been copied from their '.../itt/idl_6.3/product/ion_6.3/' directory tree. The most typical web server software is Apache and Apache's most typical directory locations on Linux are '/var/www/' or '/usr/local/apache...' Whether the web server is Apache or no, most users who install ION Script end up putting files into the CGI Script subdirectory of their web server's directory tree (e.g. '/var/www/cgi-bin/'). These users should look to remove the files 'ion-i', 'ion-p', 'ion-I' and 'ion-P' from that directory. Users who install ION Java usually end up with a directory tree named 'IONJava' rooted right below their web server's public HTML directory (e.g. '/var/www/htdocs/' on Apache). Those users should "cd" to that public HTML directory, see if 'IONJava' exists there, and then remove the whole tree with "rm -rf ./IONJava". (If you have had more than one ION installation on this host, then you may also see a sibling 'IONJavabackup' directory. You will probably want to remove this, as well.)
STEP 6: That should leave only the main directory for all Exelis Visual Information Solutions products, the 'ITT' directory. This is usually installed in '/usr/local/ITT/'. At this point, you simply have to decide whether you just want to remove one version of IDL by cd'ing to '/usr/local/ITT/' and running "rm -rf ./idl_6.3", or whether you want to remove the whole 'ITT' directory tree by cd'ing to '/usr/local/' and running "rm -rf rsi".
Important Note: On these last two steps exercise caution, if you are still using on this local host IDL or ENVI that has been installed on other machines on your network or in other directories on the local host!!!
STEP 7: Clean up your home directory if you are no longer running IDL from this local host
Users, who have started from a login on this local host IDL of any version even just one time, will find in their "ls -a" output in their home directories a '.idl' subdirectory. This subdirectory stores custom user preferences (for all versions of IDL ever used while logged onto this host). It also stores information about the state of a user's last IDL session. This directory can be deleted, if you are no longer going to be using IDL from any machine while logged into this host. (There is, by the way, no fatal danger in removing this directory; you simply lose preferences that you may have stored and used for some length of time.)
STEP 8: Clean up your shell resource files
Users, who have had the IDL installation on their machine for a while, may have adjusted their shell resource files according to instructions we provide in our Installation documentation. The files in question should normally just be in your user's home directory, and should all be prefaced by a period (e.g. .cshrc, .profile, etc.). If you, then, run the following commands:
and inspect the output, you should identify all lines in your shell resource files that are no longer relevant and can be edited out.
STEP 9: Finally, the following are directories and/or files in a user's home directory that may have very IDL-specific commands or configuration instructions in them: .flexlmrc, .assistant, and .Xdefaults. Other software programs might use these configuration files or directories, so examine their contents closely before you either delete the files or delete any specific lines from them. IDL-specific lines are usually very obvious.
That should remove all traces of Exelis VIS product installations on your host.