Use of Standard Packages

Earlier versions of Parallels Pro Control Panel customized a number of key services to resolve issues, enhance security, and improve the performance of hosting domains. While these customizations provided a superior hosting environment, they also impacted flexibility in managing these services and increased the latency period for releasing critical service security patches.

Parallels Pro removes customizations made by Parallels Pro Control Panel to critical services enabling self-managed deployment of services. However, Parallels Pro Control Panel retains customizations to certain services. Since these are no longer available or supported, Parallels Pro Control Panel is providing these as a value added enhancement.

The services that are customized are those that are originally available in the tarball format. Parallels Pro Control Panel uses the RPM format for managing services. However, certain services are released by vendors only in the tarball format requiring Parallels Pro Control Panel to convert these services to the RPM format and thus customize them.

However, the source RPMs of these services (containing Parallels Pro Control Panel customizations) will be made available for download and use to customers whenever a security patch is released by the service vendor, prior to the official release from Parallels Pro. This enables you to use the source RPMs and self-create the RPM packages for installation on to an Parallels Pro Control Panel server as soon as a security patch for the service is released. Note that when you self-upgrade RPMs with a release from the service vendor, you must restart the service after the upgrade to ensure effective functioning of the service.

The following table provides the list of customized and non-customized RPMs.

List of standard packages used (non-customized RPMs)

analog

xinetd

apache 2.0

net-snmp

gettext

quota

imap

sendmail

mod_perl (Apache 2.0)

mysql

mod_ssl (Apache 2.0)

gcc

mx

make

openssh

perl

openssl

php

postgresql

proftpd

python2

telnet

webalizer

awstats

Name of the customized RPM

Why you should not customize the RPM

cronolog

  • Converted the tarball into an RPM
  • Resolved issues concerning the date and time format of log file names

frontpage

Converted the tarball into an RPM

majordomo

  • Modified the configuration file
  • Included security fixes
  • Modified the build process so as to enable it to be built by non-root users

mod_jk

Modified for improved integration with Apache

perl-Quota

Changed to support quotas on multiple Linux kernel

versions

apache-mod_fastcgi

Resolved session timeout issues

poprelay

Created an RPM for the script

phpMyAdmin

Converted the tarball into an RPM

squirrelmail

Converted the tarball into an RPM

vacation

Converted the tarball into an RPM

mivaempressa

Converted the tarball into an RPM

mivamerchant_unl

Converted the tarball into an RPM

tomcat

Converted the tarball into an RPM

halcyon

Converted the tarball into an RPM