Re: [gridengine users] deciding spool directory location

2012-01-13 Thread Reuti
Am 13.01.2012 um 17:33 schrieb Chris Dagdigian: Whoa. If there is a tool out there that gives users access to debug and info from the spool area I'd love to hear about it and get it out into the community. One of the downsides to spool locations is that they are usually only accessible to

Re: [gridengine users] My notes on building Open GridScheduler 2011.11 on RedHat/CentOS 6.x based systems

2012-01-13 Thread CB
Hi Chris, Thank you for your posting. It's good to have such detailed build instructions. I have some comments based on my experience below. For the IzPack requirement, GE requires 4.1.1 version specifically to build the GE install GUI properly. When I tried to build it using any later version

Re: [gridengine users] My notes on building Open GridScheduler 2011.11 on RedHat/CentOS 6.x based systems

2012-01-13 Thread Burian, John
On 1/12/12 5:45 PM, Chris Dagdigian d...@sonsorol.org wrote: Tried to reverse engineer my crusty old build environment into something that I (or even others) can actually replicate or follow. Going to try similar for 32bit binaries as well as document the process for RHEL/CentOS 5.x based

Re: [gridengine users] My notes on building Open GridScheduler 2011.11 on RedHat/CentOS 6.x based systems

2012-01-13 Thread Rayson Ho
On Fri, Jan 13, 2012 at 1:10 PM, Burian, John john.bur...@nationwidechildrens.org wrote: I recently went through building GE2011.11 on a RedHat/CentOS 5.x system. I wonder, is there a reason why you chose not to use the JRE, Ant, etc. packages from the RH/CentOS distribution? Admittedly, the

Re: [gridengine users] qconf -sh fails on Centos 4 guest.

2012-01-13 Thread Simon Matthews
On Thu, Jan 12, 2012 at 10:36 PM, Rayson Ho ray...@scalablelogic.comwrote: Good! That means qconf is waiting for the master's response but not getting it. If an IP filter or firewall is configured on that node, then it is very likely to be the cause. Make sure that firewalls are turned off

Re: [gridengine users] Use of a job context (was: Available values in prolog)

2012-01-13 Thread Michael Coffman
Thanks for the input Comments below. On Fri, Jan 13, 2012 at 7:26 AM, Reuti re...@staff.uni-marburg.de wrote: Hi, Am 13.01.2012 um 02:03 schrieb Reuti: snip But a nice solution could be the usage of the job context. This can be set by the user on the command line, and your job can

Re: [gridengine users] Grid Engine complains about backslash in username when user is logged in with Active Directory account

2012-01-13 Thread Rayson Ho
I don't have access to a system with Active Directory account management, so I will need your help. Can you run the following commands on your system and send us the output?? 1) id 2) in $SGE_ROOT/utilbin/architecture/, run: ./checkuser -check userid (ie. remove the ADdomain in

Re: [gridengine users] Grid Engine complains about backslash in username when user is logged in with Active Directory account

2012-01-13 Thread Rayson Ho
Thanks, so simply stripping off the ADdomain does not cut it... Then 2 more commands: 1) ./checkuser -check BSI\\userid1 echo $? 2) ltrace su - BSI\\userid1 /tmp/outfile.txt (press CTRL-D to quit the shell) Feel free to strip everything - just send me the parameters to the getpwnam() call.