Ah!

Right in front of my eyes and it is very clear. I am very sorry about missing such good document. I read this when I was configuring GT4 WS GRAM and that section was not relevant then.

Later it became necessary to use GRAM2 for Pegasus and I started working configuring it. It was my fault that I did not come back to this document!

This must be the case and thank you for your advice again.

Cheers,
Yoichi

--------------------------------------------------------------------------
Yoichi Takayama, PhD
Senior Research Fellow
RAMP Project
MELCOE (Macquarie E-Learning Centre of Excellence)
MACQUARIE UNIVERSITY

Phone: +61 (0)2 9850 9073
Fax: +61 (0)2 9850 6527
www.mq.edu.au
www.melcoe.mq.edu.au/projects/RAMP/
--------------------------------------------------------------------------
MACQUARIE UNIVERSITY: CRICOS Provider No 00002J

This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of Macquarie E-Learning Centre Of Excellence (MELCOE) or Macquarie University.

On 22/10/2008, at 1:53 AM, Charles Bacon wrote:

On Oct 21, 2008, at 9:44 AM, Yoichi Takayama wrote:

Hi Charles,

Yes, I have firewalls between all hosts. (After this, I will read again the http://dev.globus.org/wiki/FirewallHowTo)

I have 2119 Gatekeeper port open on the main globus service host.

However, do I need to add GLOBUS_TCP_PORT_RANGE to this? I don't think that your document mentioned it, if it is the case. Am I mistaken?

The example xinetd entry from 
http://dev.globus.org/wiki/FirewallHowTo#Configuring_the_pre-WS_GRAM_Gatekeeper.2FJob-Manager_to_use_GLOBUS_TCP_PORT_RANGE

does, in fact, mention GLOBUS_TCP_PORT_RANGE in the xinetd entry for the gatekeeper.


Charles

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to