Globus Toolkit

Installing the Globus Toolkit on both Suse 10.1 and 10.2 machines, I encountered one major difference. Using the latest stable release, 4.0.3 source code version, installation for 10.2 went without trouble. However, installing for the 10.1 distribution gave me a bug during the make and was fixed using an update from the GTK advisories. The problem originated from a buggy gcc that 10.1 doesn't address. From the advisories page simply download globus_js-0.5 which corresponds to the fix for bug 4315.

Need a server cert that has no password. Commands are:

(1) change directory into the grid-security directory: cd /etc/grid-security

(2) Generate the server key (with password): openssl genrsa -des3 -out server.key 1024

(3) Generate certificate *without a password*: openssl rsa -in server.key -out server.pem

(4) Create CSR (Certificate Signing Request) to affirm that the server key is valid. The server.pem is used in place of server.key as we don’t require a password:
openssl req -new -key server.pem -out server.csr

The information you are about to be asked to enter information will be incorporated into your certificate request as the Distinguished Name or a DN of the signed cert. [ If you enter ‘.’, the field will be left blank ]

Hi
Does someone know how to render the following rsl valid also for the jobmanager-condor?

&
(executable=/bin/sh)
(arguments= -c "sleep 100;date +%s" )

Hi've noticed that with this rsl the jobmanager-pbs ( either jobmanager-fork) works fine but
the jobmanager-condor seems to fail during arguments parsing

globusrun -w -s -r grid0003/jobmanager-condor '&(executable=/bin/sh)(arguments=-c "sleep 1;date +%s")'
sleep: too few arguments
Try `sleep --help' for more information.

while

globusrun -w -s -r grid0003/jobmanager-pbs '&(executable=/bin/sh)(arguments=-c "sleep 1;date +%s")'

Hi
Does someone know how to render the following rsl valid also for the jobmanager-condor?

&
(executable=/bin/sh)
(arguments= -c "sleep 100;date +%s" )

Hi've noticed that with this rsl the jobmanager-pbs ( either jobmanager-fork) works fine but
the jobmanager-condor seems to fail during arguments parsing

globusrun -w -s -r grid0003/jobmanager-condor '&(executable=/bin/sh)(arguments=-c "sleep 1;date +%s")'
sleep: too few arguments
Try `sleep --help' for more information.

while

globusrun -w -s -r grid0003/jobmanager-pbs '&(executable=/bin/sh)(arguments=-c "sleep 1;date +%s")'

Hi
Does someone know how to render the following rsl valid also for the jobmanager-condor?

&
(executable=/bin/sh)
(arguments= -c "sleep 100;date +%s" )

Hi've noticed that with this rsl the jobmanager-pbs ( either jobmanager-fork) works fine but
the jobmanager-condor seems to fail during arguments parsing

globusrun -w -s -r grid0003/jobmanager-condor '&(executable=/bin/sh)(arguments=-c "sleep 1;date +%s")'
sleep: too few arguments
Try `sleep --help' for more information.

while

globusrun -w -s -r grid0003/jobmanager-pbs '&(executable=/bin/sh)(arguments=-c "sleep 1;date +%s")'

The following instructions will setup the Globus Client on any Linux Box. The examples in the instructions use a ficticious machine 10.0.0.33 named grid.lab.ac.uab.edu

GIIS is running on Medusa for a long time.

The files to edit to set it up:

grid_info_resource_register.conf

grid_info_policy.conf

grid_info_resource_ldif.conf

MyProxy-Server configuration done in myproxy-server.config file in the /etc directory. Just set allowed connection to * for right now.

Starting Myproxy-server for a single connection:

myproxy-server -d

I have configured globus on Nori to directly submit jobs to the condor pool. This basically means that the gram job manager in Globus is now replaced with the condor job manager. So any jobs submitted to Globus on Nori should go directly to the condor pool. I am testing out the configuration.

__Globus Toolkit 2.4 SDK__ and __Client__ bundles have been installed on proc1 and located in /opt/globus-2.4. Commands like grid-proxy init and globusrun seem to be running fine. The globus hello world program runs fine too.
I had also previously installed GPT in proc1 at /opt/gpt. While building I encountered an error which was solved when I unset the environment variable LANG.