Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: Patching up servers

  • Subject: Re: Patching up servers
  • From: Roy Schestowitz <newsgroups@schestowitz.com>
  • Date: Tue, 26 Jul 2005 16:39:00 +0100
  • Newsgroups: alt.www.webmaster
  • Organization: schestowitz.com / Manchester University
  • References: <42e50de1$0$12878$cc9e4d1f@news.dial.pipex.com> <Xns969F424F49640gandalfparker@208.201.224.154> <dc5f8o$2bn9$1@godfrey.mcc.ac.uk> <dc5i3u01msg@news2.newsguy.com> <kysFe.61475$1_2.24543@fe25.usenetserver.com>
  • Reply-to: newsgroups@schestowitz.com
  • User-agent: KNode/0.7.2
Ignoramus5833 wrote:

> On Tue, 26 Jul 2005 10:39:22 -0400, Tina - AxisHOST, Inc.
> <tpeters@axishost.com> wrote:
>>
>> Its also a really bad idea.   Security patches, etc. must be done and
>> many of those require a reboot.
> 
> I cannot think of a single security patch that I needed to apply in
> the last 4 or so years, that required a reboot. About 5 years ago
> there was a kernel bug that mandated a new kernel. The rest of my
> upgrades usually boil down to doing

You can also run a mirror on a separate server and turn over the traffic
(the aqueduct) to the second server while the other server gets patched up.
It is then a question of how quickly you can physically move the wires.
Whether it's worth the hours of invested time depends on the purpose of the
server and its applications. If it is a proxy used to connect two mission
critical computers, there might be no alternative.

Roy

-- 
Roy S. Schestowitz
http://Schestowitz.com

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index