From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Search machine is ready |
Date: | 2006-02-14 23:24:42 |
Message-ID: | 43F266BA.3040003@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> Unless we decide to move it to a different search platform, this machine
>> should not change -- ever. Production machines don't change.
>
> Hmm ... obviously Red Hat is a mirage, because their entire business
> model is built on the fact that production machines *do* require
> updates. Especially ones that provide services to the net, and
> therefore can't be completely hidden behind a firewall.
>
> Somebody's got to be responsible for updating the software on this
> server, and being prepared to do so on short notice, and being prepared
> to update any part of it from kernel on up.
I was not speaking about updates. I was talking about something such as
recompiling apache to add a php module. Of course we have to apply
security updates etc..
And we are prepared to do so on short notice, I blindly assumed that CMD
would be responsible for a good portion of this as we offered to host
the environment in the first place.
I wasn't looking for a plug and run(away) solution for the community.
Sincerely,
Joshua D. Drake
>
> regards, tom lane
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-02-14 23:41:01 | Re: Search machine is ready |
Previous Message | Tom Lane | 2006-02-14 23:16:05 | Re: Search machine is ready |