[pca] Can pca check two different local sources?

[Rajiv Gunja]

Craig,
This is not the answer you are looking for, but here is a simple way to keep
your proxy server up to date.

1. Add a cronjob to download Xref file daily or monthly, depending on your
policy.
2. Add a cronjob to download Patches monthly, using "--fromfiles" option. I
usually have Solaris 10 and Solaris 9 config files on my Proxy server, thus
I am covered on both OSes.

Why do I use this than have proxy download on-demand? Sometimes Oracle's
download facility might be down, so I do not want find that when I am ready
to kick off patching.

Since I did not understand your question fully, I will try to answer with
what I understood.
1. Create 2 pca.conf files, pca.conf.local pointing to local FS and
pca.conf.proxy pointing to the pca-proxy server.
2. Create a script to first try to download the patches from the local FS
using --cffile=pca.conf.local Capture all failed patches (notinFS.lst)
(meaning they are not present on the local FS).
3. Create a logical block to use pca-proxy server using
--cffile=pca.conf.proxy to download the patches listed in file notinFS.lst.

Hope this answers your question / gives you ideas.

-GGR
--
Rajiv G Gunja
Blog: http://ossrocks.blogspot.com


On Fri, Sep 23, 2011 at 23:28, Craig S. Bell <craig.s.bell at gmail.com> wrote:

>   Perhaps you can help me with this use case.  My pca clients need to use a
> local caching proxy to download patches from Oracle.  pca-proxy.cgi stores
> newly-downloaded patches onto a shared FS.  Most of my clients can read from
> this same FS.
>
>   If network performance were ideal, I would just point patchurl at the
> proxy, and be done with it.  In this case, it's usually faster for the
> client to grab patches directly from the FS rather than transferring each
> one via HTTP (either directly, or through the proxy CGI).
>
>   So I want the best of both worlds -- check the filesystem first, then
> automatically fall back to the proxy if needs be.   The problem is that my
> client's patchurl was already set to file://something.  This is like a
> hybrid of your two local server usage scenarios.
>
>   Can I somehow configure pca to look on the share first, then query the
> proxy server if any of the desired patches are not present?  I should say
> that I want patchdir to be somewhere different altogether, so I can stage
> patches locally on each client.
>
>   A unique patchdir would also allow me to mount my share read-only.  Also,
> I think the proxy should always handle the storing of newly acquired patches
> -- otherwise there might be a race while I'm magically using both methods in
> one download transaction.
>
>   Is there some way to combine both local server methods in this fashion?
> Please let me know if I overlooked a better solution. =-)  Thanks...
> -cheers, CSB
>
> Craig S. Bell
> Senior UNIX Engineer
> http://linkedin.com/in/craigsbell
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.univie.ac.at/pipermail/pca/attachments/20110925/40952560/attachment.html>