Hi Burt,
My sincere apologies that we didn't catch this sooner!
What does the -a option do in older versions of UberFTP? Is it really
okay to silently ignore it, or do we have to convert it to another
option? Or do we need to add some functionality to UberFTP?
I think that we can do something like make a patch for UberFTP (at
least, if we're not talking about adding major functionality), test it
out with you, and share it with the UberFTP folks so they can integrate
it into a future version. This might be the fastest route to a fix.
Let me know the details of the -a option, and we can work out a patch.
By the way, I'll be in all-day meetings (at Fermilab!) Thursday and
Friday, so I might be slow to respond for a couple of days.
Thanks,
-alain
-----------------------------------------------------------------
Alain Roy vdt-support@opensciencegrid.org
VDT Support http://vdt.cs.wisc.edu/support.html
> Hi folks,
>
> We've just noticed an incompatibility between uberftp 1.x and 2.0.
> Previously uberftp accepted a -a option and it is currently invoked by
> gLite's WMS wrappers when submitting to OSG sites (uberftp foo.bar.baz
> -a GSI etc).
>
> As of VDT 1.10.1k, you're shipping uberftp 2.0, which notes -a as an
> invalid option and exits.
>
> For backwards-compatibility, is it possible to build uberftp to silently
> ignore the -a option? I'm not sure what the timescale is on modifying
> the gLite wrappers to do uberftp version detection (although I am
> pursuing that as well).