Cleaning up patches?

• Previous message: Chris Adams: "Summary: 5.1B pk3 cluster FS and file atimes"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Sat, 11 Sep 2004 18:02:41 -0500
To: tru64-unix-managers@ornl.gov

I have a system that started with 5.1A, went through several patch kits,
was upgraded to 5.1B, had TruCluster added, and went through several
customer specific patches and patch kits. At each patch, I've always
chosen to make the patches reversible. The backups take a chunk of disk
space, which isn't a big problem, but I'd like to clean them up (I have
no plans to reverse any patches at this point).

Also, the software/patch "database" in /usr/.smdb. is getting large
(there are 3200 files in there). This is a problem, as it significantly
slows down all patch operations. Checking prereqs for installing a
patch takes way too long; when installing 5.1B patch kit 4, the prereq
stage took something like 45 minutes. When I installed kit 4 on a
freshly installed 5.1B system, the prereq checking took just a couple of
minutes. Is there a way to clean this up, so future patch operations
don't take longer and longer?

There is a lot of redundancy in there; for example, this morning I
installed a second version of a CSP that supersedes the first version I
got. However, both versions still show as "installed" in a "setld -i"
inventory.

-- 
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

• Previous message: Chris Adams: "Summary: 5.1B pk3 cluster FS and file atimes"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]