This topic of using Golbus Connect vs another form of web based client is
interesting, and relevant to our situation as well.
As Markus pointed out, while the Globus Connect client is extremely useful
the ports used (outbound tcp 2223 and 5-51000 if I recall) are commonly
blocked by organizati
>
> http://www.globus.org/toolkit/docs/latest-stable/admin/quickstart/#quickstart
>
> Maybe this developer guide too?
> http://www.globus.org/toolkit/docs/5.2/5.2.2/appendices/developer/
>
> Thoughts?
>
> -Stu
>
> On Oct 19, 2012, at Oct 19, 6:09 AM,
Has the idea of placing the documentation on a wiki where it could be
updated by community members been discussed? Perhaps by users with a
Globus Online login?
Pete
On Wed, Oct 17, 2012 at 10:58 AM, Stuart Martin wrote:
> Hi John,
>
> Thanks for your thoughts. We'll look to improve the GT doc b
Hi Gabriel,
Though users can execute binaries in /usr/local, root permissions are
needed to write there, which can be verified with ls -ld /usr/local -
thus the need for sudo when building in /usr/local. (Of course this is
not needed when building in home.)
As for running gsissh with sudo, try ru
Hi there,
I've seen the zero KB file issue when there are firewall issues.
Specifically, it looks like you have traffic allow one direction but
not the other.
It may be working between EC2 instances due to them being in the same
zone, and traffic is handled differently than for outside requests.
Trying to build globus 5.0.4 on RHEL 6 (with RH perl RPMs) fails with:
[user@blah]$ make gridftp
/usr/local/globus-5.0.4/sbin/gpt-build
-srcdir=source-trees-thr/core/source gcc64dbgpthr
Subroutine Compress::Zlib::gzFile::gzseek redefined at
/usr/local/share/perl5/Compress/Zlib.pm line 220.
Undefin
