why patches take so long

From: Mike Broderick (broderic@MIT.EDU)
Date: Wed Oct 29 2003 - 00:04:21 EST


Is it normal for Tru64 patches to take an extraordinary amount of time?
Do others see this too?

I've always thought patching Tru64 took too long but was usually
installing large patch kits (hundreds of patches) so didn't think much
of it. This past week I had to install PK#5 on 5.1a plus a single file
customer specific patch (fix ps output wrt brackets). The CSP which
replaces just one file and rebuilds the kernel took as long as 27
minutes (not including the reboot) on an ES40 w/ four 500Mhz processors
and 10GB mem. On other DS20s two CPUs and 4-8GM mem it took no less
than 15 minutes. I realize that the patch process may not take
advantage of multiple CPUs, but 27 minutes to install a single file is
ridiculous.

There are parts where the process just sits there for 5 minutes or more
with no output and I can't figure out what it's doing at that point.
I'm in single user mode so I can't see what's going on from another
login. Is it possible that it's waiting for something that isn't there
so it eventually times out after waiting a few minutes (a guess)? I'm
hoping there's some explanation that I could work around to speed the
process up.

                                                                                             
_Mike



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:41 EDT