Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
WMSX examples | ||||||||
Line: 20 to 20 | ||||||||
mkdir -p /tmp/$USER/glite cp -rd $HOME/.glite/* /tmp/$USER/glite/ export GLITE_USER_HOME=/tmp/$USER/glite | ||||||||
Changed: | ||||||||
< < | (for bash), or | |||||||
> > | (for bash), or | |||||||
## Make new .globus directory and export it: chmod -R 755 /tmp/$USER/globus >&/dev/null rm -rf /tmp/$USER/globus | ||||||||
Line: 37 to 35 | ||||||||
mkdir -p /tmp/$USER/glite cp -rd $HOME/.glite/* /tmp/$USER/glite/ setenv GLITE_USER_HOME /tmp/$USER/glite | ||||||||
Changed: | ||||||||
< < | (for tcsh). This ensures that the necessary files are accessible even after your AFS tickets expire (as they are copied to some local directory). | |||||||
> > | (for tcsh). This ensures that the necessary files are accessible even after your AFS tickets expire (as they are copied to some local directory). | |||||||
Simple job submission with traditional JDL files | ||||||||
Line: 56 to 52 | ||||||||
Log onto the Grid: | ||||||||
Changed: | ||||||||
< < | > voms-proxy-init -voms your_vo | |||||||
> > | > glite-voms-proxy-init -voms your_vo | |||||||
# If your job is expected to be long, also get long term authentication:
> myproxy-init -d -n | ||||||||
Line: 82 to 78 | ||||||||
> killall java # <- This is necessary due to a WMSX bug. # If myproxy-init was used, i.e. for long term jobs: > myproxy-destroy -d | ||||||||
Changed: | ||||||||
< < | > voms-proxy-destroy | |||||||
> > | > glite-voms-proxy-destroy | |||||||
An educative example for simple interactive job submission may be found here: interactive.tar.gz. This works in a similar way as the simplejob.tar.gz example. | ||||||||
Line: 102 to 98 | ||||||||
Log onto the Grid: | ||||||||
Changed: | ||||||||
< < | > voms-proxy-init -voms your_vo | |||||||
> > | > glite-voms-proxy-init -voms your_vo | |||||||
# If your jobs are expected to be long, also get long term authentication:
> myproxy-init -d -n | ||||||||
Line: 128 to 124 | ||||||||
> killall java # <- This is necessary due to a WMSX bug. # If myproxy-init was used, i.e. for long term jobs: > myproxy-destroy -d | ||||||||
Changed: | ||||||||
< < | > voms-proxy-destroy | |||||||
> > | > glite-voms-proxy-destroy | |||||||
Mass submission of chained jobs: parameter scan with long calculations | ||||||||
Line: 146 to 142 | ||||||||
Log onto the Grid: | ||||||||
Changed: | ||||||||
< < | > voms-proxy-init -voms your_vo | |||||||
> > | > glite-voms-proxy-init -voms your_vo | |||||||
# If your jobs are expected to be long, also get long term authentication:
> myproxy-init -d -n | ||||||||
Line: 172 to 168 | ||||||||
> killall java # <- This is necessary due to a WMSX bug. # If myproxy-init was used, i.e. for long term jobs: > myproxy-destroy -d | ||||||||
Changed: | ||||||||
< < | > voms-proxy-destroy | |||||||
> > | > glite-voms-proxy-destroy | |||||||
Deleted: | ||||||||
< < | ||||||||
-- AndrasLaszlo - 04 Nov 2008 | ||||||||
Deleted: | ||||||||
< < | ||||||||
|