<font color="#3333ff"><font face="verdana,sans-serif">Craig,</font></font><div><font color="#3333ff"><font face="verdana,sans-serif">This is not the answer you are looking for, but here is a simple way to keep your proxy server up to date.</font></font></div>
<div><font color="#3333ff"><font face="verdana,sans-serif"><br></font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif">1. Add a cronjob to download Xref file daily or monthly, depending on your policy.</font></font></div>
<div><font color="#3333ff"><font face="verdana,sans-serif">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.</font></font></div>
<div><font color="#3333ff"><font face="verdana,sans-serif"><br></font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif">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.</font></font></div>
<div><font color="#3333ff"><font face="verdana,sans-serif"><br></font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif">Since I did not understand your question fully, I will try to answer with what I understood.</font></font></div>
<div><font color="#3333ff"><font face="verdana,sans-serif">1. Create 2 pca.conf files, pca.conf.local pointing to local FS and pca.conf.proxy pointing to the pca-proxy server.</font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif">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).</font></font></div>
<div><font color="#3333ff"><font face="verdana,sans-serif">3. Create a logical block to use pca-proxy server using --cffile=pca.conf.proxy to download the patches listed in file notinFS.lst.</font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif"><br>
</font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif">Hope this answers your question / gives you ideas.</font></font></div><div><font color="#3333ff"><font face="verdana,sans-serif"><br></font></font></div>
<div><span class="Apple-style-span" style="color: rgb(51, 51, 255); font-family: verdana, sans-serif; ">-GGR</span></div><div><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">--</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">
<span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Rajiv G Gunja</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Blog: <a href="http://ossrocks.blogspot.com" target="_blank">http://ossrocks.blogspot.com</a></span><br>
<br><br><div class="gmail_quote">On Fri, Sep 23, 2011 at 23:28, Craig S. Bell <span dir="ltr"><<a href="mailto:craig.s.bell@gmail.com">craig.s.bell@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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.<br>
<br> 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).<br>
<br> 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.<br>
<br> 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.<br>
<br> 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.<br>
<br> 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<br><font color="#888888"><br>Craig S. Bell<br>Senior UNIX Engineer<br>
<a href="http://linkedin.com/in/craigsbell" target="_blank">http://linkedin.com/in/craigsbell</a><br>
</font></blockquote></div><br></div>