Following up for the web archives:

1. I've updated the configure scripts to now check for libtorque as well
as libpbs -- whatever you've got, we'll find.  This will be included in
all new versions of Open MPI, and will start showing up in the nightly
snapshots tonight.

2. There *may* be a bug in Torque 2.1.0p0 with regards to the TM system.
For those who care, I'm following up with the Torque developers -- see
http://www.clusterresources.com/pipermail/torquedev/2006-May/000216.html
for the thread.


> -----Original Message-----
> From: Jeff Squyres (jsquyres) 
> Sent: Tuesday, May 16, 2006 5:00 PM
> To: 'Open MPI Users'
> Subject: RE: [OMPI users] tm interface
> 
> Doh!  We weren't informed that they renamed their libraries 
> nor that they had changed something internally such that our 
> current support would not work.  That's somewhat disappointing.  :-(
> 
> I'll have to download the latest Torque and see what's up...
>  
> 
> > -----Original Message-----
> > From: users-boun...@open-mpi.org 
> > [mailto:users-boun...@open-mpi.org] On Behalf Of Brock Palen
> > Sent: Tuesday, May 16, 2006 4:53 PM
> > To: us...@open-mpi.org
> > Subject: [OMPI users] tm interface
> > 
> > What is the status of updating OMPI for use with the new  
> > torque-2.1.0p0 ?  Their libs were redone,  you can edit the 
> > configure  
> > script to replace all the -lpbs with -ltorque  and ompi will build  
> > but when you try to run a job under tm you get this error.  
> This was  
> > under OSX server 10.3.x
> > 
> > [aon038.engin.umich.edu:02438] pls:tm: start_procs returned 
> error -13
> > [aon038.engin.umich.edu:02438] [0,0,0] ORTE_ERROR_LOG: Not 
> found in  
> > file rmgr_urm.c at line 177
> > [aon038.engin.umich.edu:02438] [0,0,0] ORTE_ERROR_LOG: Not 
> found in  
> > file rmgr_urm.c at line 365
> > [aon038.engin.umich.edu:02438] mpirun: spawn failed with errno=-13
> > 
> > Brock
> > _______________________________________________
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
> > 

Reply via email to