Henry Nebrensky wrote:
> On Fri, 16 Dec 2005, Maarten Litmaath wrote:
>
>>...
>>You may need to unset GLOBUS_TCP_PORT_RANGE on the WN, as some firewalls
>>cannot handle the same port being used in rapid succession by the client
>>(LCG-2_7_0 will unset it by default, on the WN).
>
>
> We've been having similar problems, so I was going to give this a go.
>
> Is it possible to do this with the current YAIM, and if so do I set
> GLOBUS_TCP_PORT_RANGE to an empty value in site-info.def, or just comment
> it out completely?
If you explicitly set it to an empty value, YAIM 2.6.0-10 will leave the
variable undefined on the WNs, while making it "20000 25000" on other nodes.
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.
> 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
|