hidden:Globus Connect: Difference between revisions

From Lsdf
Jump to navigationJump to search
mNo edit summary
mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:


Prereqs:
Prereqs:
* enable EPEL acces (see http://fedoraproject.org/wiki/EPEL/FAQ)
* enable EPEL acces. If the EPEL repos are in yum.repos.d then you're probably OK. (see http://fedoraproject.org/wiki/EPEL/FAQ)
* time must be synchronised (ntp).
* time must be synchronised: Check if an ntpd is running.


Install of Globus Connect
Install of Globus Connect
Line 20: Line 20:
<pre>
<pre>
yum install globus-connect-server
yum install globus-connect-server
</pre>

In my case the $releasever variable was returning 6.5 although the repo urls have locations for just 6. I fixed this by forcing the variable to 6:

<pre>
yum --releasever=6 install globus-connect-server
</pre>
</pre>

Latest revision as of 15:03, 11 May 2014

Steps taken to install globus connect

Some of the information is gleaned from https://www.globus.org/

Prereqs:

Install of Globus Connect

  • update the repo dir for easy access to the globus packages:
rpm -hUv http://www.globus.org/ftppub/gt5/5.2/stable/installers/repo/Globus-5.2.stable-config.redhat-6Server-1.noarch.rpm

This will install the Globus repo file in /etc/yum.repos.d/Globus-5.2.stable-config.redhat.repo. If you are installing on another distribution or version select another RPM. Globus maintains a list of RPMs that will install the proper repo file for you here: http://www.globus.org/ftppub/gt5/5.2/stable/installers/repo/.

  • install the Globus Connect Package:
yum install globus-connect-server

In my case the $releasever variable was returning 6.5 although the repo urls have locations for just 6. I fixed this by forcing the variable to 6:

yum --releasever=6 install globus-connect-server