Download the latest version of CommuniGate Pro here
Log into your Linux server with super-user (i.e. root) privledges
Using the Red Hat Package Manager (the .rpm file):
Using the Debian Package Manager (the .deb file):
Using other systems (the .tgz file):
The CommuniGate Pro software will be installed into the /opt directory by default.
The installer will create the /etc/rc.d/init.d/CommuniGate startup script. To make the CommuniGate Pro Server start and stop automatically when the system restarts, the installer adds the startup file links to the /etc/rc.d/rcn.d directories.
If your system was running some standalone SMTP server/MTA (such as Postfix, Exim or sendmail), you need to stop and disable that server.
For example, you can use this command to disable sendmail (need to restart the server computer to take effect):
Or these commands to stop and remove Postfix:
The Installer renames the /bin/mail program into the /bin/LegacyMail. If you decide to uninstall the CommuniGate Pro system, the legacy mail program will be renamed back to /bin/mail.
The Installer creates the new /bin/mail application - a drop-in substitution for the legacy mail program.
The Installer creates the "base directory" /var/CommuniGate and the Server uses it by default. You can move the "base directory" to any other location. In this case, open the /etc/rc.d/init.d/CommuniGate file and update it.
Restart the system or launch the start-up script manually:
Proceed with the Initial Configuration.
Some older versions of Linux (such as RedHat 9.0, SuSE 9.1 and some other distributions) used a very unstable version on the NPTL p-threads library. To provide a workaround for these versions of the Linux OS, the CommuniGate Pro startup script uses the LD_ASSUME_KERNEL=2.4.1 command to make the Linux linker use the old, more stable version of the p-threads library.
When the old p-threads library is used, each CommuniGate Pro thread is seen as a separate process when you use the ps and top system utilities. This is normal: all those "processes" are actually CommuniGate Pro Server threads, and they share all their resources - VRAM, file descriptors, etc.
Linux kernels prior to 2.6.13 have critical flaws in their NFS client implementations. If you plan to use the Linux OS as your Dynamic Cluster backends, make sure that your kernel version is 2.6.13 or higher.