[pca] specifying a specific date instead of minage

Bliss, Kevin L Bliss.Kevin at con-way.com
Thu Aug 28 00:15:04 CEST 2008




Kevin Bliss
Con-way Enterprise Services
503 450-6124 (v)
971 678-0402 (c)
bliss.kevin at con-way.com
Telecommute - Every Tuesday

-----Original Message-----
From: pca-bounces at lists.univie.ac.at [mailto:pca-bounces at lists.univie.ac.at] On Behalf Of amy.rich at tufts.edu
Sent: Wednesday, August 27, 2008 1:15 PM
To: PCA (Patch Check Advanced) Discussion
Subject: Re: [pca] specifying a specific date instead of minage


bliss.kevin> You can either make a local copy of the patchdiag.xref on all of bliss.kevin> the servers on the same day.

amy.rich>But then you're once again limited to running pca with --nocheckxref or it will update whenever you run, say, pca -l.  The time between patching on dev and production can be as much as three months or sometimes more.

You don't use --nocheckxref, you point to the local patchdiag.xref file you copied.

bliss.kevin> Or can run pca -d (whatever other flags you use) to download bliss.kevin> instead of install on the same day on all of the servers.

That defeats the purpose of having a central patch repository and takes up too much space on the thousands of client nodes.  It also doesn't delete the patches once it's installed them, so you'd have to manually clean them out after you've finished a patch cycle.




More information about the pca mailing list