Jim that completely resolved my problem.
Thank you saludos, José Luis Gordillo Ruiz Coordinación de Supercómputo UNAM El 30/07/2014, a las 20:21, Basney, Jim <jbas...@illinois.edu> escribió: > Hi José, > > My guess is that you want to set the GLOBUS_HOSTNAME environment variable [1] > to the desired hostname when starting up the globus-gatekeeper, i.e., add > "export GLOBUS_HOSTNAME=hostname" in your /etc/init.d/globus-gatekeeper > script or "env = GLOBUS_HOSTNAME=hostname" in your > /etc/xinetd.d/globus-gatekeeper file. According to [2] the globus-gatekeeper > has honored the GLOBUS_HOSTNAME environment variable for a few years now. > > -Jim > > [1] http://toolkit.globus.org/toolkit/docs/latest-stable/ccommonlib/pi/ > [2] https://globus.atlassian.net/browse/GRAM-134 > > On 7/30/14, 7:26 PM, j...@super.unam.mx wrote: > Hi, > > I'm pretty sure this question has been answered in the past, but I couldn't > find the answer > > I have a GRAM service running on a "login-node" in a cluster. As usually > happens, this node has two network interfaces. > I can successfully submit jobs to the node, however, the contact string > returned is built using the hostname of the internal network interface. > > Is there a way to change that? > > thank you in advance, > > > saludos, > > José Luis Gordillo Ruiz > Coordinación de Supercómputo > UNAM
