> > I'm having a hard time getting my head around the fact that pca is > > very system-dependent. > > It has to be. A system may have any set of packages and patches > installed, PCA won't assume that any two systems are exactly the > same. So it sees what's (already) there, and tells you what's > missing. If you as an administrator know that two systems are equal, > it's fine to download the patches only once on one fo them and re-use > them later on the second system.
This is exactly why I put an additional layer on top of PCA to allow it to run against explorers of system, so you can run PCA only on one server for your whole parc ;-) On Wed, 19 Oct 2011 11:17:39 +0200 Martin Paul <mar...@par.univie.ac.at> wrote: > Lisa, > > Others have already described various options you have. As for my 2 > cent: Take a look at the PCA documentation, especially the parts > about setting up a local patch server (in your situation, a PCA local > caching proxy might suit best, and there are detailed step-by-step > instructions in the docs) and about creating patch reports for remote > machines. > > As seen in other follow-ups, many people use PCA just as one tool in > their patching framework. Therefore I kept PCA as general as > possible, and you'll have to find your own way that fits best to your > surroundings. > > > Martin. > -- Thomas Gouverneur _____ _ | ____|___ _ __ (_)_ __ | _| / __| '_ \| \ \/ / | |___\__ \ |_) | |> < |_____|___/ .__/|_/_/\_\ Network |_| SPRL TVA: BE6836018011 T: +32 498 23 00 40 W: http://espix.net M: <tho...@espix.net>
