Just in case there is one person on this list that isn't aware...
and so it begins...
Craig
-------- Forwarded Message --------
From: nahant-list@redhat.com Reply-To: nahant-list@redhat.com To: nahant-list@redhat.com Subject: Red Hat Enterprise Linux 4 Update 3 Availability Announcement Date: Tue, 07 Mar 2006 19:32:51 -0500
Red Hat is pleased to announce the availability of Update 3 for the Red Hat Enterprise Linux 4 family of products including:
- Red Hat Enterprise Linux AS 4 for x86, AMD64/EM64T, Itanium, POWER, S/390 and zSeries
- Red Hat Enterprise Linux ES 4 for x86, AMD64/EM64T, Itanium
- Red Hat Enterprise Linux WS 4 for x86, AMD64/EM64T, Itanium
- Red Hat Desktop 4 for x86 and AMD64/EM64T
This update includes the following enhancements:
Availability of a full set of updated installable CD ISO with OS package updates and install-time support for new hardware.
Availability of updated Extras ISO images with third party package updates.
Hardware support enhancements:
- Improved support for larger system configurations with
- up to 64 logical CPUs on AMD64 and EM64T 64 bit platforms through a new "largesmp" kernel variant depending on hardware certification.
- up to 64 logical CPUs on PPC (and IA64 carried forward from Update 2) with the existing "smp" kernel variant depending on hardware certification.
- Technology preview for support of very large system configurations on IA64 (up to 256 logical CPUs) and PPC (up to 128 logical CPUs). ** NOTE: These are the certification limits Red Hat is currently aiming at depending on partner and customer testing feedback. Theoretical limits referenced in the Kernel notes might be higher. Independent of any technology preview or theoretical limit, the actual supported system configuration limits that depend on real partner hardware to be certified are documented on the Red Hat website at http://www.redhat.com/en_us/USA/rhel/details/limits/
- IA64 multi-core support
- Driver updates including cciss, hangcheck-timer, ipmi_devintf, ipmi_msghandler, ipmi_poweroff, ipmi_si, ipmi_watchdog, mptbase, e1000, ixgb, tg3, aacraid, ahci, ata_piix, iscsi_sfnet, libata, qla2100, qla2200, qla2300, qla2322, qla2xxx, qla6312, sata_nv, sata_promise, sata_svw, sata_sx4, sata_vsc, cifs
- Driver additions including bnx2, dell_rbu, ib_mthca, megaraid_sas, qla2400, typhoon
Security enhancements: * Execshield updates * Begin use of gcc FORTIFY_SOURCE build option in some package updates * SELinux policy updates * Updated kernel key management support
System tools enhancements: * SystemTap dynamic system instrumentation tool enhancements including technology preview for broader hardware architecture support * Kernel crash dump analysis tool enhancements * Technology preview of the Frysk execution analysis framework, for more information visit http://sourceware.org/frysk/ * Updated OpenIPMI support
Storage enhancements: * Improvements to autofs / automount * Device-mapper snapshot and multipath I/O improvements * Support for 4GB-versions of Fibre Channel HBAs * NFS access control lists, asynchronous I/O
Networking enhancements: * Technology preview of Infiniband support via the OpenIB stack
Updated third-party Java packages on the Extras CD
Security updates, bug fixes, and feature enhancements to numerous system packages
Errata Advisories describing specific changes in Update 3 are available online at: https://rhn.redhat.com/errata/rhel4as-errata.html (AS) https://rhn.redhat.com/errata/rhel4es-errata.html (ES) https://rhn.redhat.com/errata/rhel4ws-errata.html (WS) https://rhn.redhat.com/errata/rh-desktop-4-errata.html (Desktop)
Release notes for this update will be available on the Red Hat documentation site at: http://www.redhat.com/docs/manuals/enterprise/
This update is available immediately to all current Red Hat Enterprise Linux subscribers via Red Hat Network. Simply run 'up2date' to retrieve the latest packages or visit the following URL to download ISO images for new installations: https://rhn.redhat.com/network/software/download_isos.pxt
Regards,
The Red Hat Enterprise Linux Team
-- nahant-list mailing list nahant-list@redhat.com https://www.redhat.com/mailman/listinfo/nahant-list
On Tue, 2006-03-07 at 17:40 -0700, Craig White wrote:
Just in case there is one person on this list that isn't aware...
and so it begins...
We're on it :)
When we release, I want everyone to remember the upstream bandwidth issues, login failures and timeouts that happened today ...
It isn't just us that have failures on release day :)
On Tue, 2006-03-07 at 19:18 -0600, Johnny Hughes wrote:
On Tue, 2006-03-07 at 17:40 -0700, Craig White wrote:
Just in case there is one person on this list that isn't aware...
and so it begins...
We're on it :)
When we release, I want everyone to remember the upstream bandwidth issues, login failures and timeouts that happened today ...
It isn't just us that have failures on release day :)
---- did upstream have some issues today? I hadn't heard.
I am not one to up2date -u/yum update the first day of a big update, preferring to allow the brave to do some final regression testing before I trounce all over my installations
;-)
Craig
I'm trying to mirror a live server onto a slave server of identical hardware. Theory being that when the master server blows up I can change the IP of the slave, restore the db's, restart a few processes and make everyone happy again.
What is the best way of doing this? Can you literally rsync / (with the exception of perhaps /proc and /tmp) and create an identical copy of the master? Is there a better way to achieve this?
I've looked at using cluster suite but I don't think the instant(ish) and automatic failover justifies the cost of the shared storage.
TIA,
-- Nick B
On Wed, 8 Mar 2006 at 10:15:50, Nick wrote:
I'm trying to mirror a live server onto a slave server of identical hardware. Theory being that when the master server blows up I can change the IP of the slave, restore the db's, restart a few processes and make everyone happy again.
What is the best way of doing this? Can you literally rsync / (with the exception of perhaps /proc and /tmp) and create an identical copy of the master? Is there a better way to achieve this?
Have a look at DRBD [1] for "shared-nothing-storage" and heartbeat [2] for failover (both part of CentOS)
[1] http://www.drbd.org/ [2] http://www.linux-ha.org/
On Wed, 2006-03-08 at 20:15 +1100, Nick wrote:
I'm trying to mirror a live server onto a slave server of identical hardware. Theory being that when the master server blows up I can change the IP of the slave, restore the db's, restart a few processes and make everyone happy again.
What is the best way of doing this? Can you literally rsync / (with the exception of perhaps /proc and /tmp) and create an identical copy of the master? Is there a better way to achieve this?
I've looked at using cluster suite but I don't think the instant(ish) and automatic failover justifies the cost of the shared storage.
hi nick,
kk I'm doing exactly what you are trying to accomplish I think.
say the power went off completely.... nothing
k...comes back on... I run the exact same daemon and scripts in 2 mirror machines. I run the daemon in the first machine...it does the checking, realizes the other machine is not serving so it takes the roaming ip address and runs w/it. Then I run the daemon in the other machine...it realizes that the other box has the ball so it assumes slave responsibilities which are to just keep checking on the master...if the slave sees where the master is having problems, it takes the roaming ip and runs with it.
while all this is going on...the master keeps syncing up the slave oh, bout ever 15 seconds... Not perfect like a big $$$$ real time warez but it's close enuf for a small place like this!
I'd say when the slave does take the ball...the whole process takes bout 30-40 seconds which I don't like but that's life... the router has to be flushed one way or other in the deal...that's bout 20 seconds on this cheepie I got because I have to warm boot it...but this whole process w/all it's shortcomings on the time deals works flawlessly tho.
John Rose
The next time you report something to this list, please _don't_ reply to a random post but create a new e-mail. This way you'll not break all thread aware e-mail clients out there (and as such more people might actually notice your post).
/Peter
On Wednesday 08 March 2006 10:15, Nick wrote:
I'm trying to mirror a live server onto a slave server of identical hardware. Theory being that when the master server blows up I can change the IP of the slave, restore the db's, restart a few processes and make everyone happy again.
What is the best way of doing this? Can you literally rsync / (with the exception of perhaps /proc and /tmp) and create an identical copy of the master? Is there a better way to achieve this?
I've looked at using cluster suite but I don't think the instant(ish) and automatic failover justifies the cost of the shared storage.
TIA,
-- Nick B
The next time you report something to this list, please _don't_ reply to a random post but create a new e-mail. This way you'll not break all thread aware e-mail clients out there (and as such more people might actually notice your post).
/Peter
My bad - how embarrassing, sorry. No one else reply to this thread for further fear of threadjacking. I'll post it again (less the In-Reply-To: header) in a few days when I've got over the shame.
-
Craig White -
Johnny Hughes -
Michael Metz [SpeedPartner] -
Nick -
Peter Kjellström -
rado