Hi Tim and Scot,
I've got two tarballs for you:
Core: http://rsv.grid.iu.edu/downloads/OSG_RSV_Core-2.3.5.tar.gz -- with
changes Tim C made, as explained in his email below
Probes: http://rsv.grid.iu.edu/downloads/OSG_RSV_Probes-2.3.3.tar.gz --
with the changes to the cacert-crl-probe that make it go find the URL
being used for CAcert updates, before using the URL for comparison data.
The perl module also has minor modifications to fix bugs or add features
that folks requested -- long pending updates that never made it to the
light of day.
I've tested both the configure script and the probe changes but more
testing would useful, as Tim pointed out.
Cheers,
Arvind
On 9/9/2008 5:41 PM, Tim Cartwright pondered:
- Hide quoted text -
> Arvind:
>
> As you are aware, the recent update to Apache revealed a problem with
> our update process -- RSV's Apache configuration is lost during an
> update. For now, we have a workaround for updates (save and restore
> the Apache configuration file). A more complete solution is to change
> the way in which configure_osg_rsv modifies the Apache configuration.
> Attached is a tarball with a proposed new configure_osg_rsv.
>
> At first, I thought that this change would be simple, but in the end I
> rewrote all of the setup_apache_for_rsv() function. As a result, it
> would be great if you could test the new code. I have tested in quite
> a bit manually in an OSG-CE install, but the more testers the better!
>
> In addition to improving the way in which the Apache configuration is
> changed, I also fixed what I'm pretty sure was a minor bug in the code
> that adds an RSV link to the main index.html file; previously, I
> believe that multiple invocations of "configure_osg_rsv
> --setup-for-apache" would result in multiple RSV links being added to
> index.html.
>
> Let us know how you would like to proceed from here. If you make a
> OSG RSV Core 2.3.5 release, for example, we would be happy to test it
> and then update it in the VDT.
>
> -- Tim
RT for crt.cs.wisc.edu
