Ooops, didn't see your reply, Michael.

Thanks for the additional details,
Erich

On Thursday 16 November 2006 15:20, Michael Edwards wrote:
> See if the documents here:
> 
> http://svn.oscar.openclustergroup.org/wiki/oscar:5.0:administration_guide:ch4.1.1_torque_overview
> 
> help.  I significantly expanded the section on torque/maui, and included
> more detailed example scripts for mpich and lam/mpi.  They are officially
> 5.0 docs, but the sections on torque/maui should be fine for 4.2.
> 
> Just as a random plug, 5.0 was released this week and is a significant
> improvement over
> 
> On 11/16/06, Shaohui Yang <[EMAIL PROTECTED]> wrote:
> >
> >  Hi, All:
> >
> >
> >
> >    I have successfully deployed the Oscar 4.2 cluster on 3 redhat EL 
> > 3.0machines ( one act as head node and other act as client nodes ) in few
> > weeks.
> >
> >
> >
> >    Now I am trying the queue system, I am a little confusing about how I
> > am going on. I don't find any words on oscar website for queueing system,
> > and I have read the documents for torque resource manager, I don't think
> > that is too much helpful.
> >
> >    I knew that oscar have many components such SIS, torque. Anybody can
> > explain how many components it has and how they work together? For its queue
> > system, how many components it has and how they work together? Before I tell
> > the users to use the "qsub" command to submit the jobs, What should I do
> > after the installation? Where I can get the help and more information for
> > it?
> >
> >
> >
> > Regards.
> >


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Oscar-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to