Re: Patch Maintainence

From: Bruce D Porter (bdp_at_ytc1.co.uk)
Date: 10/30/03 

Date: Thu, 30 Oct 2003 19:29:04 +0000

On Wed, 29 Oct 2003 21:49:12 -0800, "Michael Vilain <vilai wrote:

> In article <tj%nb.18118$Gq.5726753@twister.nyc.rr.com>,
> "Rodrick Brown" <rbrown-no-spam@doitt.nyc.gov> wrote:
>
>> Ok we have finally hit 150 servers here at work and its becoming a major
>> pain to rollout patches how are most people handling this ?
>>
>> I'm just looking for a robust and flexible way of rolling out system patches
>> across 150 servers or so, kinda something like SUS for microsoft.
>>
>> Is there anything more flexible than automounting all the servers to the
>> patch server ?
>>
>> I was looking at cfengine it looks tedious but might be worth the effort if
>> enough time is spent deploying it anyone have experience with it ?
>>
>> I think SUN recently released a tool to patch over the web but this does me
>> no good since 90% of my servers are internal only.
>
> There isn't one that Sun provides. Doing patchadd from the terminal is

I presume you are talking about

https://sunsolve.sun.com/patchpro/README.2.2

> the only way I've seen to do this. I would be very hesitant to do
> anything with cfengine or rdist/rsync, even if I had lots of machines
> that were identically installed via a Jumpstart template.
>
> If you have 150 servers that are each one-offs, my heart goes out to
> you. You'll have to plan 150 separate upgrades. If you have groups
> that are identical installs from a jumpstart template, that's good. You
> can spend a month of weekends each twice a year upgrading systems with
> the latest Recommended patch bundle, assuming you can tolerate the
> downtime. If your 150 systems can't tolerate the scheduled downtime,
> then move on to other projects until something breaks and you have to 

-- 
	Bruce
######################################################
# The internet is a huge and diverse community and   #
# not every one is friendly" 		             #
#        http://www.ytc1.co.uk                       #
######################################################

Relevant Pages

  • Re: Patch Maintainence
    ... > pain to rollout patches how are most people handling this? ... > across 150 servers or so, kinda something like SUS for microsoft. ... > I think SUN recently released a tool to patch over the web but this does me ... DeeDee, don't press that button! ...
    (comp.unix.admin)
  • Re: Patch Maintainence
    ... > pain to rollout patches how are most people handling this? ... > across 150 servers or so, kinda something like SUS for microsoft. ... > I think SUN recently released a tool to patch over the web but this does me ... DeeDee, don't press that button! ...
    (comp.unix.solaris)
  • Re: Patch Maintainence
    ... > pain to rollout patches how are most people handling this? ... > across 150 servers or so, kinda something like SUS for microsoft. ... > I think SUN recently released a tool to patch over the web but this does me ... DeeDee, don't press that button! ...
    (comp.sys.sun.admin)
  • Re: Patch Maintainence
    ... >> pain to rollout patches how are most people handling this? ... >> across 150 servers or so, kinda something like SUS for microsoft. ... >> I think SUN recently released a tool to patch over the web but this does me ... If your 150 systems can't tolerate the scheduled downtime, ...
    (comp.unix.admin)
  • Re: Patch Maintainence
    ... >> pain to rollout patches how are most people handling this? ... >> across 150 servers or so, kinda something like SUS for microsoft. ... >> I think SUN recently released a tool to patch over the web but this does me ... If your 150 systems can't tolerate the scheduled downtime, ...
    (comp.unix.solaris)