On Wed, Jul 11, 2012 at 9:38 AM, John Young wrote:
> Hmmm... If it was an OS issue, I would expect both queues to behave
> the same way since both are under the same OS, but they don't.
Again, as a normal user & then as root, run an interactive shell - but
let me clarify, *outside of Grid Engine
On 07/10/2012 04:30 PM, Rayson Ho wrote:
On Tue, Jul 10, 2012 at 4:23 PM, John Young wrote:
With this in place, it seems odd that from one of my queues I
get a default setting for the number of descriptors of 1024.
So I have two questions really:
1. Why am I getting different behavior from th
On Tue, Jul 10, 2012 at 4:23 PM, John Young wrote:
> With this in place, it seems odd that from one of my queues I
> get a default setting for the number of descriptors of 1024.
>
> So I have two questions really:
>
> 1. Why am I getting different behavior from the two queues?
Could be OS issue -
On 07/10/2012 04:14 PM, Rayson Ho wrote:
On Tue, Jul 10, 2012 at 4:02 PM, John Young wrote:
If you really have a real use-case for setting the # of descriptors in
the queue config, then let us know and we can implement that in OGS/GE
(... when time permits).
Well... I have an engineer here w
On Tue, Jul 10, 2012 at 4:02 PM, John Young wrote:
>> If you really have a real use-case for setting the # of descriptors in
>> the queue config, then let us know and we can implement that in OGS/GE
>> (... when time permits).
>>
> Well... I have an engineer here who want to run a 2048 core job.
On 07/10/2012 03:47 PM, Rayson Ho wrote:
The number of file descriptors is not part of the queue limit, see the
message I sent to the list 2 months ago:
http://gridengine.org/pipermail/users/2012-May/003705.html
If you really have a real use-case for setting the # of descriptors in
the queue co
The number of file descriptors is not part of the queue limit, see the
message I sent to the list 2 months ago:
http://gridengine.org/pipermail/users/2012-May/003705.html
If you really have a real use-case for setting the # of descriptors in
the queue config, then let us know and we can implement
I have a short test job that I can submit to different
queues on my cluster that appear to be configured the
same, but I get different results. Here is the job:
---
#!/bin/tcsh
#
#$ -N show-limits
#$ -S /bin/tcsh
#$ -o show-limits.out
#$ -e show-limits.err
