Index: [Article Count Order] [Thread]

Date:  Sun, 15 Mar 2009 17:34:49 -0700
From:  "Doug Harvey" <dwh1958 (at mark) gmail.com>
Subject:  [coba-e:15327] Re: Dovecot Auth I/O Leak Error
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <49bd9eaf.47c2f10a.4817.0add (at mark) mx.google.com>
In-Reply-To:  <5FB654D7-EDCD-4222-B507-1316F476B0E1 (at mark) housleyconsulting.com.au>
X-Mail-Count: 15327

This is true. You do want to keep them up to date. Being cautious is a good
thing, (as we've learned over the last couple of weeks) but at the same
time, it really is a good idea to have a test server sitting around to run
these updates on first before doing them on the production systems.

Doug


-----Original Message-----
From: Xin CHEN [mailto:xchen (at mark) housleyconsulting.com.au] 
Sent: Sunday, March 15, 2009 5:13 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:15324] Re: Dovecot Auth I/O Leak Error

It looks like I was wrong about not updating. I always thought never  
update unless have to :)
OK. I will pick one of the Server to start with.

Thanks guys.

-tim

On 16/03/2009, at 10:29 AM, Chris Gebhardt - VIRTBIZ Internet wrote:

> Xin CHEN wrote:
>> Hi Jimmy,
>> Thanks for the comments. We have other Servers running just fine  
>> without update as well. The reason I am afraid of updating system  
>> is that I saw a lot of emails that says "after updating, we have  
>> problems with ..... " These are all production Servers. So I don't  
>> want to update unless have to. Has anyone had this kind of error  
>> messages before?
>
> Yikes!   We update our BQ servers weekly and our BX servers nightly.
> I would suggest if you have several production servers that you roll  
> out your updates on a test system, or do what you need to in order  
> to ensure your safety.  But absolutely keep your system up to date!
>
> -- 
> Chris Gebhardt
> VIRTBIZ Internet Services
> Access, Web Hosting, Colocation, Dedicated
> www.virtbiz.com | toll-free (866) 4 VIRTBIZ