Faq t2b: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 18: | Line 18: | ||
export http_proxy=http://qproxy.wn.iihe.ac.be:3128 | export http_proxy=http://qproxy.wn.iihe.ac.be:3128 | ||
export https_proxy=http://qproxy.wn.iihe.ac.be:3128 | export https_proxy=http://qproxy.wn.iihe.ac.be:3128 | ||
* For ssh traffic (example using CERN) | * For ssh traffic, through a server you have access to (example using CERN) | ||
:: edit your '''.ssh/config''' file ===> | :: edit your '''.ssh/config''' file ===> | ||
<pre> | <pre> | ||
Revision as of 12:55, 23 November 2016
List of the UIs / mX machines:
- m0 , m1 , m2 , m3 => 10 minutes of CPU time per process
- m5 , m6 , m7 , m8 , m9 => 5 hours of CPU time per process
Keep ssh connection to UI open:
Add option ' -o ServerAliveInterval=100 ' to your ssh command
Send a job to the local cluster:
qsub -q localgrid -o script.stdout -e script.stderr [-l walltime=<HH:MM:SS>] myscript.sh
Access internet faster from the UIs
Since our bandwidth with internet is limited and extremely expansive, you need to use the another one:
- For http/https traffic (uses the university traffic)
export http_proxy=http://qproxy.wn.iihe.ac.be:3128 export https_proxy=http://qproxy.wn.iihe.ac.be:3128
- For ssh traffic, through a server you have access to (example using CERN)
- edit your .ssh/config file ===>
host github.com
ProxyCommand ssh MYUSERNAME@lxplus.cern.ch nc github.com 22
User MYUSERNAME