I am trying to determine a best approach to patching some redhat AS installations we have at my company. Because we require a soak in period in a test environment before fixes can be applied to production boxes, I was thinking of maintaining a repository for rpms somewhere that I could later use to go install on the production servers. This way I wouldn't run into the problem of a newer patch being released in between our test period and the time I go to install on production.
Anyway, my question is this. The following was pulled from redhat's site regarding up2date's options.
Quote:
You may keep a local directory of packages yourself. You can ask up2date to look for these first:
[user@localhost user]$ up2date -k (or –packagedir)This will be followed by a colon delimited list of directory paths to check before attempting to download newer ones.
|
If I incorporate this type of option when installing on my production servers, will it only install from the package directory I specified (assuming the package is there), or will it look in my directory, and then still check RHN for a newer package? In the second case, will it install what I tell it, or the newer package? And honestly, I guess it wouldn't be that much more difficult to just rpm all the packages and maintain my own list of dependencies.
Anyway, and advice or answers would be greatly appreciated. Thanks a bunch.
