hi
It may help that one go through some old documents with
N1GE
oracle gridengine
howto/tips and some training pdf
and good tutorial video on the web etc
regards
On 7/11/2012 11:53 AM, Joseph Farran wrote:
On 07/10/2012 01:24 PM, Rayson Ho wrote:
On Tue, Jul 10, 2012 at 3:51 PM, Reuti
wrote
sorry, one may add the docs by sun/oracle on sge n1ge oge are not the
best but they do contain some useful info
regards
On 7/11/2012 12:13 PM, Hung-Sheng Tsao Ph.D. wrote:
hi
It may help that one go through some old documents with
N1GE
oracle gridengine
howto/tips and some training pdf
and good
On 07/10/2012 01:24 PM, Rayson Ho wrote:
On Tue, Jul 10, 2012 at 3:51 PM, Reuti wrote:
Joseph,
To debug the difference in behavior:
1) make sure that you can always reproduce the job failure.
2) then submit jobs to a node that fails the job& to a node that does
not fail the job.
3) in the
On Tue, Jul 10, 2012 at 3:51 PM, Reuti wrote:
>> Failure was that user's .bashrc were not being read. In each user's
>> account, I have it sourcing a system wide shell script which sets certain
>> things up, like our module environment configuration and so nothing was
>> being setup.
>
> Yep,
Am 10.07.2012 um 21:20 schrieb Joseph Farran:
> On 07/10/2012 11:38 AM, Rayson Ho wrote:
>> On Tue, Jul 10, 2012 at 1:48 PM, Joseph Farran wrote:
>>> I was using the same identical script, so it's still a mystery why the
>>> script ran on some nodes while it failed on others, but now with this ch
On 07/10/2012 11:38 AM, Rayson Ho wrote:
On Tue, Jul 10, 2012 at 1:48 PM, Joseph Farran wrote:
I was using the same identical script, so it's still a mystery why the
script ran on some nodes while it failed on others, but now with this change
it works on all nodes and that is good enough.
Th
On Tue, Jul 10, 2012 at 1:48 PM, Joseph Farran wrote:
> I was using the same identical script, so it's still a mystery why the
> script ran on some nodes while it failed on others, but now with this change
> it works on all nodes and that is good enough.
Those settings affect whether the global l
On 07/10/2012 02:37 AM, Reuti wrote:
Am 10.07.2012 um 09:29 schrieb Hung-Sheng Tsao Ph.D.:
hi
to use -S /bin/bash
need
shell_start_mode posix_behavior
you may also want to add bash to login_shells in qconf -mconf global
regards
On 7/10/2012 1:21 AM, Joseph A. Farran wrote:
Hello.
I
Am 10.07.2012 um 09:29 schrieb Hung-Sheng Tsao Ph.D.:
> hi
> to use -S /bin/bash
> need
> shell_start_mode posix_behavior
>
> you may also want to add bash to login_shells in qconf -mconf global
>
> regards
>
> On 7/10/2012 1:21 AM, Joseph A. Farran wrote:
>> Hello.
>>
>> I have a cluste
hi
to use -S /bin/bash
need
shell_start_mode posix_behavior
you may also want to add bash to login_shells in qconf -mconf global
regards
On 7/10/2012 1:21 AM, Joseph A. Farran wrote:
Hello.
I have a cluster with Rocks 5.4.3 (SL) and I believe this is a Rocks
issue but not sure.
I have
Hello.
I have a cluster with Rocks 5.4.3 (SL) and I believe this is a
Rocks issue but not sure.
I have my "sge_request" with the default shell of:
-S /bin/bash
My OGE scripts that start with "#!/bin/bash" work on some compute
11 matches
Mail list logo
