By mwu on

I've received 2 emails from site5 telling me of down time due to critical security upgrades for ruby on rails, php, and apache.

I've received no such emails from opensourcehost. (I assume they haven't done them, since I assume I'm notified of planned downtime.)

although I've been very unhappy with site5, this definitely raises my evaluation of them. I am wondering what communication others have received from their hosts.

⋅ Categories: Drupal 4.7.x

Comments

OSH’s picture

OSH commented

From OpenSourceHost

Planned downtimes are posted in the support forums (please read your welcome email for offsite support information). Updating apache and php require extremely little downtime, and are done as needed. They do not require a reboot. Kernel updates require a reboot. These types of security patches are a no brainer, and any host that has been around for any length of time does them (or will learn the hard way).

The real security of a server (given that the basics are done) is determined by the various other software/hardware used to lock down, secure, and maintain the integrity of a server. Keeping a server secure requires many layers, and is a daily job. Server security is not a set it and forget it routine.

Please don't assume anything. If you have questions about OSH, feel free to open a help desk ticket. Thank you.

mwu’s picture

mwu commented

very interesting.

thank you.

sorry for my mistaken assumption.

I wonder if it is possible to keep a running log of patches so that I don't need to wonder about anything critical.

I had received an email from a third host about downtime (no reason specified) so it seemed to me that they were also patching.

I'm glad you had a chance to post here and show the drupal community how responsive opensourcehost is. As I wrote, I have been very happy with opensourcehost, and very unhappy with site5.

styro’s picture

styro commented

Without any loss of service, so I wouldn't judge them on that criteria alone.

eg:

# apache2ctl graceful

Will allow all new Apache processes to use the new files/config, while the existing processes are left to finish current requests and then die off normally to be replaced by updated ones. This means that you can update Apache or PHP without any downtime.

--
Anton
New to Drupal? | Forum posting tips | Troubleshooting FAQ
Example Knowledge Base built using Drupal