Am 04.12.2013 um 21:59 schrieb Wiegers, Bert:
> According to the man-page of queue_conf
> the kill -9 command should have been sent by default (we tried this first).
> This killscript below was an attempt to fix the problem.
> Both don't work.
Then it might be promising to get a tight SSH integra
According to the man-page of queue_conf
the kill -9 command should have been sent by default (we tried this first).
This killscript below was an attempt to fix the problem.
Both don't work.
Bert
> -Original Message-
> From: Reuti [mailto:re...@staff.uni-marburg.de]
> Sent: Wednesday, D
Am 04.12.2013 um 17:47 schrieb Wiegers, Bert:
> our setup is
>
> sge_conf:
> qlogin_command
> /export/opt/SGE-8.1.6/utilbin/lx-amd64/qlogin_wrapper.sh
>
> cat /export/opt/SGE-8.1.6/utilbin/lx-amd64/qlogin_wrapper.sh
> #!/bin/sh
> HOST=$1
> PORT=$2
> /usr/bin/ssh -Y -p $PORT $HOST
That is something we noticed, as well. The 100% CPU usage, I mean. Is
that a known thing?
Tina
On 04/12/13 16:50, Wiegers, Bert wrote:
btw.
on the nodes where I am logged on with qlogin the CPU-usage from the shepherd
is always on 100%
-Original Message-
From: Reuti [mailto:re...
btw.
on the nodes where I am logged on with qlogin the CPU-usage from the shepherd
is always on 100%
> -Original Message-
> From: Reuti [mailto:re...@staff.uni-marburg.de]
> Sent: Wednesday, December 04, 2013 5:33 PM
> To: Wiegers, Bert
> Cc: users@gridengine.org
> Subject: Re: [griden
our setup is
sge_conf:
qlogin_command
/export/opt/SGE-8.1.6/utilbin/lx-amd64/qlogin_wrapper.sh
cat /export/opt/SGE-8.1.6/utilbin/lx-amd64/qlogin_wrapper.sh
#!/bin/sh
HOST=$1
PORT=$2
/usr/bin/ssh -Y -p $PORT $HOST
queue_conf:
terminate_method /export/opt/SGE-8.1.6/scripts/cas
Am 04.12.2013 um 17:19 schrieb Wiegers, Bert:
> Hi *,
>
> we are using a qlogin wrapper script, as mentioned below.
> It looks like that this setup prevents the sge to reach the terminate_method.
You defined a custom "terminate_method"? Can you please post it?
-- Reuti
> Bert
>
>> -Origi
Hi *,
we are using a qlogin wrapper script, as mentioned below.
It looks like that this setup prevents the sge to reach the terminate_method.
Bert
> -Original Message-
> From: users-boun...@gridengine.org [mailto:users-boun...@gridengine.org] On
> Behalf Of Wiegers,
> Bert
> Sent: Tuesd
Dear Reuti,
This is helpful for me. Thank you very much!
Best regard,
Yong WU
2013/12/4 Reuti
> Am 04.12.2013 um 12:34 schrieb Yong Wu:
>
> > Dear Reuti,
> >
> > The part of submitted script:
> > #start
> > #$ -pe mpi4 8
> > #$ -l h="compute-0-27|compute-0-30"
> > #$ -q all.q
> > #$ -
Am 04.12.2013 um 12:34 schrieb Yong Wu:
> Dear Reuti,
>
> The part of submitted script:
> #start
> #$ -pe mpi4 8
> #$ -l h="compute-0-27|compute-0-30"
> #$ -q all.q
> #$ -v LD_PRELOAD=/home/wuy/bin/libtime.so.1
> #end
>
> $ qconf -sp mpi4
> pe_namempi4
> slots
Dear Reuti,
The part of submitted script:
#start
#$ -pe mpi4 8
#$ -l h="compute-0-27|compute-0-30"
#$ -q all.q
#$ -v LD_PRELOAD=/home/wuy/bin/libtime.so.1
#end
$ qconf -sp mpi4
pe_namempi4
slots
user_lists NONE
xuser_listsNONE
start_pr
Hi,
Am 04.12.2013 um 11:31 schrieb Yong Wu:
> I want to set a environment variable on slave nodes, and I did this in my
> submitted script:
> #$ -v LD_PRELOAD=/home/wuy/bin/libtime.so.1
The variable will bet set at execution time of the script, wherever it's
executed. Due you mean:
- the lo
Dear all,
I want to set a environment variable on slave nodes, and I did this in my
submitted script:
#$ -v LD_PRELOAD=/home/wuy/bin/libtime.so.1
But this variable can only take effect on master node. How to set a
environment variable on slave nodes?
Any help about this issue will be apreci
13 matches
Mail list logo
