smpatch fails when proxy patch server can't access Sun
I think most would agree that a key benefit of the patch proxy is to have the patches locally, especially when the Sun patch site is unavailable.
I found today that if my patch proxy server can't reach Sun, then all client requests fail trying to retrieve detectors.
I would agree that it should show errors and indicate that it cannot connect to Sun to retrieve the most current files. However I think that the patch proxy should serve up requests based on the stored files (patchdb.zip and detectors.jar) and patches.
Can someone at Sun please verify this is the case and comment.
Thanks,
JB
[631 byte] By [
jwbledsoe] at [2007-11-26 6:05:19]
# 1
I believe that the currently in development "Onsite Edition" of Update Connection is perhaps better suited to serve the patches locally rather than the Update Connection proxy which really only currently provides a route for the client machines to connect to the outside world and retrieve patches.
So to answer your question - I believe that the proxy currently behaves as expected and the "Onsite Edition" which is in development should provide the local repository features you mentioned.
Having said that I agree that it would be beneficial to have this feature in the current proxy and i'll pass the request on internally for feedback and a possible RFE.
# 3
First thanks for all the info and following it up with them.Second, is there a way we can get them to quit changing the names all the time, tell em to pick something and stick with it.;-)
