HIVE and CloudLinux difference & compatibility
Is Hive compatible with CloudLinux and what are the differences?
- CloudLinux throttles the users - which in turn can generate more memory usage and more unhappy clients
- Hive imposes hard resource limits - which are designed to protect the server from overload and allow you to oversell resources
- in addition mod_limits provides connection and load limits
- and mod_balance introduces protection from aggressive clients by delaying the execution of dynamic content and throttling the serving of static content
- CloudLinux gives you only an overall picture of the resource usage
- provides detailed resource usage information for CPU, Memory and I/O.
- provides APIs so you can access this information.
- gives you an easy access to the resource usage information from ALL of your servers
- keeps history information for all the collected data
- CloudLinux uses its own internally developed mechanism called CageFS to do account isolation
- Hive uses the well defined chroot(2) mechanism
- Hive also provides a few other security fixes
- mod_hive patches an important security hole in Apache where a non-root user can create a symlink to a file that is readable by the web server and access it even if it is within the directory of another user
- mod_rangelimit protects apache from abuse using the Range header attack
What Hive gives you more?
- 7 different PHP versions
- Provides a cPanel, DirectAdmin and Plesk plugins so you can check your account resource usage from within the control panel
- Provides cPanel plugin for easily changing the PHP version (per folder)
- Provides cPanel plugin for easily adding/changing PHP variables (per folder)
To some extend Hive and ClouldLinux functionality overlaps, though different technologies are used. Hive applies resource usage limitations through RLimits, while Cloud Linux applies kernel limits on resource usage. Also Hive is isolating the accounts through a chroot mechanism. Cloud Linux have a similar concept - the CageFS (still in beta as per the official available information).
What CloudLinux does is to give you the possibility to limit resource usage for a single user. For example set 10% resource usage limitation and no user will be able to use more than 10% of the server resources at any given time.
What Hive does is impose resource usage limits per process. For example at no given time a single process can use more then 512MB memory or run longer then 120 seconds. You can find more information in the Hive limits section.
The above 2 points are where HIVE and Cloudlinux overlap. There are few more features that come with HIVE and they are described below:
Overall, Hive is pretty much shared hosting oriented product. It was created with the purpose to have your shared server serving requests to best of its ability, rather than throttling user processes*. It also provides you with detailed statistics about CPU consumption and script executions for users on the server. Also Hive comes with 6 different PHP versions, cPanel plugins for easy PHP version change and PHP variables management, resource usage statistics for your clients directly in cPanel and more. The 1H software development is targeted specifically for the needs of webhosting providers and their clients.
HIVE also includes "Automated reaction to resource abuse" system. You can setup automated actions depending on User statistics gathered by Hive. Upon enabling this option (OFF by default) you setup specific limits on CPU usage based on script executions and CPU time. Limits can be set for script executions made via web access and cron jobs. You can specify what automated actions to be taken upon users reaching those limits. You can decide to set up automatic suspend or web traffic redirects for such accounts and thus protect better the other users on the server, notify the account owners and offer them a higher-end solution, or apply a combination of both approaches.
You can see how the user interface for setting up the limits looks like in the User Limits section.
CloudLinux is no longer compatible with Hive. Apache can execute PHP files either through Hive or through CloudLinux, but not through both simultaneously. This means that you can use either Hive or CloudLinux, but not both at the same time. All other 1H products (Guardian, Hawk and Digits) can be installed on a server running CloudLinux though. However HIVE that is basically interchangeable with CloudLinux cannot be run simultaneously with CloudLinux. One can work without the other, but they cannot work together. You will be using either Hive or CloudLinux for PHP execution.