On 01/10/2012 12:55 PM, Gene Poole wrote:
We've got about 200 existing servers running CentOS/RHEL 5.6 and all new
servers are being provisioned using CentOS/RHEL 6.1. So that everything
is consistent we need to upgrade the servers running CentOS/RHEL 5.6. I've
searched the CentOS wiki,
We've got about 200 existing servers running CentOS/RHEL 5.6 and all new
servers are being provisioned using CentOS/RHEL 6.1. So that everything
is consistent we need to upgrade the servers running CentOS/RHEL 5.6. I've
searched the CentOS wiki, the Red Hat site, and the internet looking for
On Tue, 10 Jan 2012 13:55:05 -0500
Gene Poole wrote:
We've got about 200 existing servers running CentOS/RHEL 5.6 and all new
servers are being provisioned using CentOS/RHEL 6.1. So that everything
is consistent we need to upgrade the servers running CentOS/RHEL 5.6. I've
searched the
Gene Poole wrote:
We've got about 200 existing servers running CentOS/RHEL 5.6 and all new
servers are being provisioned using CentOS/RHEL 6.1. So that everything
is consistent we need to upgrade the servers running CentOS/RHEL 5.6. I've
searched the CentOS wiki, the Red Hat site, and the
On Tue, Jan 10, 2012 at 1:35 PM, m.r...@5-cent.us wrote:
We've got about 200 existing servers running CentOS/RHEL 5.6 and all new
servers are being provisioned using CentOS/RHEL 6.1. So that everything
is consistent we need to upgrade the servers running CentOS/RHEL 5.6. I've
searched the
Les Mikesell wrote:
On Tue, Jan 10, 2012 at 1:35 PM, m.r...@5-cent.us wrote:
We've got about 200 existing servers running CentOS/RHEL 5.6 and all
new servers are being provisioned using CentOS/RHEL 6.1. So that
everything is consistent we need to upgrade the servers running
CentOS/RHEL
On Tue, Jan 10, 2012 at 3:35 PM, m.r...@5-cent.us wrote:
What we do is build one, then create /boot/new and /new on the next
server, rsync over to them, then mkdir /boot/old and /old, and (using
zsh with modules loaded) mv * old, mv old/lost+found ., mv
old/new/* ., make sure a few things
On 1/15/09, Kenneth Burgener kenn...@mail1.ttak.org wrote:
On 1/9/2009 9:49 AM, Robert Nichols wrote:
If a hard reboot is what you are attempting to avoid, with 'kexec' even
the Linux kernel can be reloaded without a hardware reset. This is
convenient if you want to avoid the long system
Michael Simpson wrote:
if you really have to have as perfect an uptime as possible then you
can actually patch a running kernel using ksplice
http://www.ksplice.com/
should only be used for critical security updates but useful nonetheless
mike
On 1/9/2009 9:49 AM, Robert Nichols wrote:
Brian wrote:
Is there a list of packages that after update require a reboot, other then
kernel?
For updates other than the kernel, there is almost always an answer
short of a full reboot. But, finding that answer and being 100%
certain
I've did some googling and have not came up with and answer yet. Is
there
a list of packages that after update require a reboot, other then kernel?
TIA
Brian
___
CentOS mailing list
CentOS@centos.org
Brian wrote:
I've did some googling and have not came up with and answer yet. Is
there
a list of packages that after update require a reboot, other then kernel?
That is a difficult question, and the answer depends on how certain you
need to be that no running process is still using the
12 matches
Mail list logo
