Joseph Farran jfar...@uci.edu writes:
Dave,
I am having the same/similar issues as Brian's but with 8.1.2.But for me,
it's even worse.
There are only two resources I can request which are mem_total and
swap_total. All others fail.
OK, thanks. I'll have another look at the code
Hi, Dave,
I tested only mem_free in my environment. We're on el6.3 running SGE
8.1.1, x86_64. My symptoms came from jobs not dispatching and turning
schedd_jobinfo on to reveal that that mem_free was an unknown parameter
on my hosts. All I know is after adding the attribute to the
Brian Smith b...@usf.edu writes:
Hi, Dave,
I tested only mem_free in my environment. We're on el6.3 running SGE
8.1.1, x86_64. My symptoms came from jobs not dispatching and turning
schedd_jobinfo on to reveal that that mem_free was an unknown
parameter on my hosts. All I know is after
Dave,
I am having the same/similar issues as Brian's but with 8.1.2.But for me,
it's even worse.
There are only two resources I can request which are mem_total and
swap_total. All others fail.
$ qrsh -l mem_total=1M
Last login: Mon Sep 10 22:02:39 2012 from login-1-1.local
Brian Smith b...@usf.edu writes:
Hi, Joseph,
Wow. Just ran into this one myself (mem_free). Adding a complex value to
each host set to mem_free=(ram on host) made for a good work-around. The
variable is still being reported, so it still reports the real mem_free
(not the value you set),
