On Mon, 19 Dec 2005, Steve Traylen wrote:
> > In LCG-2_7_0 the WN will never have the port range defined, while the rest
> > will use what was specified by the admin.
>
> This may actually break something though I am casting my mind back a long
> way so my memory may be patchy.
>
> With multiple stream replications when using edg-rm commands at least they
> went non passive. This was certainly a problem at NIKHEF and it was there
> request that this was added.
>
> Maybe that has gone completly away now with lcg-utils.
Even edg-rm (i.e. Globus) was fixed, where possible, to avoid such problems:
due to a limitation in GridFTP, when multiple streams are used, the connection
is made in the direction of the transfer; most WN have no inbound connectivity,
so cannot receive (but can store) files using multiple streams.
With an explicit "-n" option the lcg-utils (and edg-rm-orig) allow the number
of streams to be set. The edg-rm by default switched to 3 for files larger
than 100 MB, but lcg-utils always use 1 by default.
> Steve
> >
> > >Or do I have to do this in the pool accounts' startup scripts?
> >
> > Indeed, you also could add scripts like these to /etc/profile.d on your WNs:
> >
> > # cat zzz_unset_port_range.csh
> > unsetenv GLOBUS_TCP_PORT_RANGE
> > # cat zzz_unset_port_range.sh
> > unset GLOBUS_TCP_PORT_RANGE
>
>
|