RE: [Queue-developers] RE: Re: just "one" more question (Monica L au)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

What command did you use to checkout of cvs?

Make sure you checkout queue-development and not queue which is about a year
old.

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/queue co
queue-development

Sam

> -----Original Message-----
> From: Hazelrig, Chris C. (Contractor - Simtech)
> [mailto:Chr...@hw...]
> Sent: 05 April 2001 20:26
> To: 'que...@li...'
> Subject: [Queue-developers] RE: Re: just "one" more question (Monica
> Lau)
> 
> 
> Greetings,
> 
> I realize this message is in response to an old mailing, but I've been
> working on other things for a while.  Anyway, I have a 
> question regarding
> the "dummylicense" Ms. Lau refers to below (Queue-developers 
> digest, Vol 1
> #47 - 4 msgs, Message 1).  I have downloaded the latest Queue 
> sources from
> CVS and did not find a file by this name.  The software that 
> I am trying to
> run using Queue does not require a license and I have been 
> unable submit any
> jobs since the queue manager performs license checks.  Is it 
> possible to
> construct the "dummylicense" file from scratch?  Any help would be
> appreciated.
> 
> Regards,
> Chris Hazelrig
> 
> > -----Original Message-----
> > From:	que...@li...
> > [SMTP:que...@li...]
> > Sent:	Friday, January 19, 2001 2:04 PM
> > To:	que...@li...
> > Subject:	Queue-developers digest, Vol 1 #47 - 4 msgs
> > 
> > Send Queue-developers mailing list submissions to
> > 	que...@li...
> > 
> > To subscribe or unsubscribe via the World Wide Web, visit
> > 	http://lists.sourceforge.net/lists/listinfo/queue-developers
> > or, via email, send a message with subject or body 'help' to
> > 	que...@li...
> > 
> > You can reach the person managing the list at
> > 	que...@li...
> > 
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Queue-developers digest..."
> > 
> > 
> > Today's Topics:
> > 
> >    1. Re: just "one" more question (Monica Lau)
> >    2. Re: just "one" more question (Mark Denni)
> >    3. Re: just "one" more question (W. G. Krebs)
> >    4. Re: just "one" more question (Eric Deal)
> > 
> > --__--__--
> > 
> > Message: 1
> > Date: Thu, 18 Jan 2001 15:33:39 -0800 (PST)
> > From: Monica Lau <ml...@al...>
> > To: que...@li...
> > Subject: Re: [Queue-developers] just "one" more question
> > Reply-To: que...@li...
> > 
> > On Tue, 16 Jan 2001, Federico Ardanaz wrote:
> > 
> > > 1) task_control seems to do nothing at all!?
> > 
> > Are you running the task_manager program on each machine as 
> where the 
> > queue daemons are running?
> > 
> > I realize that some of the programs may not be working 
> correctly.  My 
> > apologies, but progress is rather slow at the moment.  I've 
> just updated 
> > W. Krebs with the new patches.  Hopefully, they'll be up 
> for people to 
> > download soon.
> > 
> > These are the necessary steps to run the programs:
> > 
> > 1) There needs to be a "my_qdir" subdirectory within the 
> standard queue 
> > directory.  The queue_manager uses the my_qdir directory to 
> store certain 
> > files.  All of these files, except for one (the "licenses" 
> file) gets 
> > created by the queue_manager.
> > 
> > 2) The "licenses" file needs to be in the my_qdir 
> subdirectory.  It stores
> > the total number of licenses that users are allowed to use 
> per license
> > feature (ie, 10 matlab licenses).  In the updated patches, 
> there is a
> > default license called "dummylicense" so that users are not 
> required to
> > specify a license(s) in order to run a job, ie, if they 
> just want to do
> > something like "queue -- ./a.out".  However, note that the number of
> > dummylicenses would limit the total number of jobs that users can
> > run.  Users can change this number if they want.  In the 
> current programs,
> > 
> > I believe that users do have to specify a license.
> > 
> > 3) In order to view what jobs are running and where they 
> are running, 
> > users simply have to look at the "status" file within the my_qdir 
> > directory.  Just a simple "cat my_qdir/status" will do.  In 
> the updated
> > patches, the queue_manager updates this status file quite often.
> > 
> > 4) Some of the variables in the queue_define.h file needs 
> to be updated 
> > before compilation.  QMANAGERHOST -- change the host name 
> of this variable
> > 
> > to be the name of the server where the queue_manager will 
> be running 
> > on.  Also, be sure to update the new directory paths of the 
> variables 
> > QDIR, AVAILHOSTS, ..., TEMPFILE.
> > 
> > 5) In order for the task_control program to work correctly, the 
> > task_manager program must be running on each server where 
> each queue 
> > daemon is running. 
> > 
> > Please let me know if anything is unclear or if there are 
> any problems.  I
> > hope this helps!
> > 
> > Regards,
> > Monica Lau
> > 
> > 
> > > 2) How can I remove (qdel in NQS) batch jobs?
> > > 3) How can I know how many jobs are running and where?
> > > 
> > > 	Federico Ardanaz
> > > 
> > > _______________________________________________
> > > Queue-developers mailing list 
> Que...@li...
> > > To unsubscribe, subscribe, or set options:
> > > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > > 
> > 
> > 
> > 
> > --__--__--
> > 
> > Message: 2
> > Date: Thu, 18 Jan 2001 22:37:35 -0800
> > From: Mark Denni <ma...@re...>
> > To: que...@li...
> > Subject: Re: [Queue-developers] just "one" more question
> > Reply-To: que...@li...
> > 
> > This is a multi-part message in MIME format.
> > --------------01742FCFB766A0EBB01A0E23
> > Content-Type: text/plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> > 
> > Monica -
> > 
> > Perhaps you can help me. I had to take the queue manager and
> > related components out so that I could configure Queue on 
> > Solaris 2.7. Otherwise, when I ran configure, it would
> > just fail, complaining that I was running a cross-compiler.
> > Has anyone else had this problem?  Has anyone successfully
> > built Queue on Solaris2.7?  I'd be very interested as well,
> > if someone has been able to interoperate between Solaris
> > and Linux with Queue.
> > 
> > - Mark
> > 
> > Monica Lau wrote:
> > > 
> > > On Tue, 16 Jan 2001, Federico Ardanaz wrote:
> > > 
> > > > 1) task_control seems to do nothing at all!?
> > > 
> > > Are you running the task_manager program on each machine 
> as where the
> > > queue daemons are running?
> > > 
> > > I realize that some of the programs may not be working 
> correctly.  My
> > > apologies, but progress is rather slow at the moment.  
> I've just updated
> > > W. Krebs with the new patches.  Hopefully, they'll be up 
> for people to
> > > download soon.
> > > 
> > > These are the necessary steps to run the programs:
> > > 
> > > 1) There needs to be a "my_qdir" subdirectory within the 
> standard queue
> > > directory.  The queue_manager uses the my_qdir directory to store
> > certain
> > > files.  All of these files, except for one (the 
> "licenses" file) gets
> > > created by the queue_manager.
> > > 
> > > 2) The "licenses" file needs to be in the my_qdir 
> subdirectory.  It
> > stores
> > > the total number of licenses that users are allowed to 
> use per license
> > > feature (ie, 10 matlab licenses).  In the updated 
> patches, there is a
> > > default license called "dummylicense" so that users are 
> not required to
> > > specify a license(s) in order to run a job, ie, if they 
> just want to do
> > > something like "queue -- ./a.out".  However, note that 
> the number of
> > > dummylicenses would limit the total number of jobs that users can
> > > run.  Users can change this number if they want.  In the current
> > programs,
> > > I believe that users do have to specify a license.
> > > 
> > > 3) In order to view what jobs are running and where they 
> are running,
> > > users simply have to look at the "status" file within the my_qdir
> > > directory.  Just a simple "cat my_qdir/status" will do.  
> In the updated
> > > patches, the queue_manager updates this status file quite often.
> > > 
> > > 4) Some of the variables in the queue_define.h file needs 
> to be updated
> > > before compilation.  QMANAGERHOST -- change the host name of this
> > variable
> > > to be the name of the server where the queue_manager will 
> be running
> > > on.  Also, be sure to update the new directory paths of 
> the variables
> > > QDIR, AVAILHOSTS, ..., TEMPFILE.
> > > 
> > > 5) In order for the task_control program to work correctly, the
> > > task_manager program must be running on each server where 
> each queue
> > > daemon is running.
> > > 
> > > Please let me know if anything is unclear or if there are 
> any problems.
> > I
> > > hope this helps!
> > > 
> > > Regards,
> > > Monica Lau
> > > 
> > > > 2) How can I remove (qdel in NQS) batch jobs?
> > > > 3) How can I know how many jobs are running and where?
> > > >
> > > >       Federico Ardanaz
> > > >
> > > > _______________________________________________
> > > > Queue-developers mailing list 
> Que...@li...
> > > > To unsubscribe, subscribe, or set options:
> > > > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > > >
> > > 
> > > _______________________________________________
> > > Queue-developers mailing list 
> Que...@li...
> > > To unsubscribe, subscribe, or set options:
> > > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > --------------01742FCFB766A0EBB01A0E23
> > Content-Type: text/x-vcard; charset=us-ascii;
> >  name="markd.vcf"
> > Content-Transfer-Encoding: 7bit
> > Content-Description: Card for Mark Denni
> > Content-Disposition: attachment;
> >  filename="markd.vcf"
> > 
> > begin:vcard 
> > n:Denni;Mark
> > tel;fax:(408) 719-4800
> > tel;work:(408) 719-4742
> > x-mozilla-html:FALSE
> > org:RedSwitch
> > adr:;;1815 McCandless Drive;Milpitas;CA;95035-8046;USA
> > version:2.1
> > email;internet:ma...@re...
> > title:Sr. UNIX Systems Administrator
> > x-mozilla-cpt:;25160
> > fn:Mark Denni
> > end:vcard
> > 
> > --------------01742FCFB766A0EBB01A0E23--
> > 
> > 
> > 
> > --__--__--
> > 
> > Message: 3
> > To: <que...@li...>
> > Subject: Re: [Queue-developers] just "one" more question
> > Date: Fri, 19 Jan 2001 09:48:52 -0500
> > From: "W. G. Krebs" <wer...@ya...>
> > Cc: <bug...@gn...>, <bug...@gn...>
> > Reply-To: que...@li...
> > 
> > 
> > This is a bug in the ./configure script, or, in reality, in the GNU
> > Autoconf 
> > program.
> > 
> > Queue_manager requires C++, so I had to add this to the configure.in
> > setup.
> > 
> > Unfortunately, GNU Autoconf does not seem to work correctly 
> with C++/g++
> > on some 
> > platforms, concluding that the C++ compiler is a cross-compiler.
> > 
> > I suppose we'll have to write the folks at autoconf to ask 
> us for help
> > with this 
> > problem, hence the CC line. [Note that queue-developers is 
> spam-proofed by
> > 
> > requiring subscriptions, so folks from bug-autoconf should 
> just reply to
> > the CC 
> > addresses. Thanks.]
> > 
> > Quoting Mark Denni <ma...@re...>:
> > 
> > > Monica -
> > > 
> > > Perhaps you can help me. I had to take the queue manager and
> > > related components out so that I could configure Queue on 
> > > Solaris 2.7. Otherwise, when I ran configure, it would
> > > just fail, complaining that I was running a cross-compiler.
> > > Has anyone else had this problem?  Has anyone successfully
> > > built Queue on Solaris2.7?  I'd be very interested as well,
> > > if someone has been able to interoperate between Solaris
> > > and Linux with Queue.
> > > 
> > > - Mark
> > > 
> > > Monica Lau wrote:
> > > > 
> > > > On Tue, 16 Jan 2001, Federico Ardanaz wrote:
> > > > 
> > > > > 1) task_control seems to do nothing at all!?
> > > > 
> > > > Are you running the task_manager program on each 
> machine as where the
> > > > queue daemons are running?
> > > > 
> > > > I realize that some of the programs may not be working 
> correctly.  My
> > > > apologies, but progress is rather slow at the moment.  I've just
> > updated
> > > > W. Krebs with the new patches.  Hopefully, they'll be 
> up for people to
> > > > download soon.
> > > > 
> > > > These are the necessary steps to run the programs:
> > > > 
> > > > 1) There needs to be a "my_qdir" subdirectory within 
> the standard
> > queue
> > > > directory.  The queue_manager uses the my_qdir 
> directory to store
> > certain
> > > > files.  All of these files, except for one (the 
> "licenses" file) gets
> > > > created by the queue_manager.
> > > > 
> > > > 2) The "licenses" file needs to be in the my_qdir 
> subdirectory.  It
> > stores
> > > > the total number of licenses that users are allowed to 
> use per license
> > > > feature (ie, 10 matlab licenses).  In the updated 
> patches, there is a
> > > > default license called "dummylicense" so that users are 
> not required
> > to
> > > > specify a license(s) in order to run a job, ie, if they 
> just want to
> > do
> > > > something like "queue -- ./a.out".  However, note that 
> the number of
> > > > dummylicenses would limit the total number of jobs that 
> users can
> > > > run.  Users can change this number if they want.  In the current
> > programs,
> > > > I believe that users do have to specify a license.
> > > > 
> > > > 3) In order to view what jobs are running and where 
> they are running,
> > > > users simply have to look at the "status" file within 
> the my_qdir
> > > > directory.  Just a simple "cat my_qdir/status" will do.  In the
> > updated
> > > > patches, the queue_manager updates this status file quite often.
> > > > 
> > > > 4) Some of the variables in the queue_define.h file needs to be
> > updated
> > > > before compilation.  QMANAGERHOST -- change the host 
> name of this
> > variable
> > > > to be the name of the server where the queue_manager 
> will be running
> > > > on.  Also, be sure to update the new directory paths of 
> the variables
> > > > QDIR, AVAILHOSTS, ..., TEMPFILE.
> > > > 
> > > > 5) In order for the task_control program to work correctly, the
> > > > task_manager program must be running on each server 
> where each queue
> > > > daemon is running.
> > > > 
> > > > Please let me know if anything is unclear or if there are any
> > problems.  I
> > > > hope this helps!
> > > > 
> > > > Regards,
> > > > Monica Lau
> > > > 
> > > > > 2) How can I remove (qdel in NQS) batch jobs?
> > > > > 3) How can I know how many jobs are running and where?
> > > > >
> > > > >       Federico Ardanaz
> > > > >
> > > > > _______________________________________________
> > > > > Queue-developers mailing list 
> Que...@li...
> > > > > To unsubscribe, subscribe, or set options:
> > > > > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > > > >
> > > > 
> > > > _______________________________________________
> > > > Queue-developers mailing list 
> Que...@li...
> > > > To unsubscribe, subscribe, or set options:
> > > > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > 
> > 
> > --__--__--
> > 
> > Message: 4
> > To: que...@li...
> > Subject: Re: [Queue-developers] just "one" more question 
> > From: Eric Deal <eri...@co...>
> > Date: Fri, 19 Jan 2001 09:12:44 -0600
> > Reply-To: que...@li...
> > 
> > 
> > Mark,
> > 
> > I started working on Solaris/Linux cross-platform Queue support
> > several months ago during some down time.  As far as I know, this
> > is still partially broken.  
> > 
> > Queue now properly handles passing jobs between big/little
> > endian systems (the first problem), but the remaining problem 
> > (that I'm aware of) is that the terminal settings are passed 
> > from "client" to "server" via the job file in the
> > native format of the submitting machine.  When this structure
> > is read by the execution machine, it will fail if it is not the
> > same platform (the termios structure varies greatly among the 
> > Unix platforms).
> > 
> > The general solution that I had in mind was on the client to map
> > all local termios settings to a common structure, or even a simple 
> > ASCII string, and use this in the job structure.  The server machine
> > would then take the information and populate its native 
> termios structure
> > with this data when parsing the job file.
> > 
> > Hopefully I'll have some more time to spend on this over the next 
> > several months.
> > 
> > Eric Deal
> > eri...@co...
> > 
> > >--0__=882569D90024C2EF8f9e8a93df938690918c882569D90024C2EF
> > >Content-type: text/plain; charset=us-ascii
> > >
> > >
> > >Monica -
> > >
> > >Perhaps you can help me. I had to take the queue manager and
> > >related components out so that I could configure Queue on
> > >Solaris 2.7. Otherwise, when I ran configure, it would
> > >just fail, complaining that I was running a cross-compiler.
> > >Has anyone else had this problem?  Has anyone successfully
> > >built Queue on Solaris2.7?  I'd be very interested as well,
> > >if someone has been able to interoperate between Solaris
> > >and Linux with Queue.
> > >
> > >- Mark
> > >
> > >Monica Lau wrote:
> > >>
> > >> On Tue, 16 Jan 2001, Federico Ardanaz wrote:
> > >>
> > >> > 1) task_control seems to do nothing at all!?
> > >>
> > >> Are you running the task_manager program on each machine 
> as where the
> > >> queue daemons are running?
> > >>
> > >> I realize that some of the programs may not be working 
> correctly.  My
> > >> apologies, but progress is rather slow at the moment.  I've just
> > updated
> > >> W. Krebs with the new patches.  Hopefully, they'll be up 
> for people to
> > >> download soon.
> > >>
> > >> These are the necessary steps to run the programs:
> > >>
> > >> 1) There needs to be a "my_qdir" subdirectory within the 
> standard queue
> > >> directory.  The queue_manager uses the my_qdir directory to store
> > certain
> > >> files.  All of these files, except for one (the 
> "licenses" file) gets
> > >> created by the queue_manager.
> > >>
> > >> 2) The "licenses" file needs to be in the my_qdir 
> subdirectory.  It
> > >stores
> > >> the total number of licenses that users are allowed to 
> use per license
> > >> feature (ie, 10 matlab licenses).  In the updated 
> patches, there is a
> > >> default license called "dummylicense" so that users are 
> not required to
> > >> specify a license(s) in order to run a job, ie, if they 
> just want to do
> > >> something like "queue -- ./a.out".  However, note that 
> the number of
> > >> dummylicenses would limit the total number of jobs that users can
> > >> run.  Users can change this number if they want.  In the current
> > >programs,
> > >> I believe that users do have to specify a license.
> > >>
> > >> 3) In order to view what jobs are running and where they 
> are running,
> > >> users simply have to look at the "status" file within the my_qdir
> > >> directory.  Just a simple "cat my_qdir/status" will do.  
> In the updated
> > >> patches, the queue_manager updates this status file quite often.
> > >>
> > >> 4) Some of the variables in the queue_define.h file 
> needs to be updated
> > >> before compilation.  QMANAGERHOST -- change the host name of this
> > >variable
> > >> to be the name of the server where the queue_manager 
> will be running
> > >> on.  Also, be sure to update the new directory paths of 
> the variables
> > >> QDIR, AVAILHOSTS, ..., TEMPFILE.
> > >>
> > >> 5) In order for the task_control program to work correctly, the
> > >> task_manager program must be running on each server 
> where each queue
> > >> daemon is running.
> > >>
> > >> Please let me know if anything is unclear or if there 
> are any problems.
> > >I
> > >> hope this helps!
> > >>
> > >> Regards,
> > >> Monica Lau
> > >>
> > >> > 2) How can I remove (qdel in NQS) batch jobs?
> > >> > 3) How can I know how many jobs are running and where?
> > >> >
> > >> >       Federico Ardanaz
> > >> >
> > >> > _______________________________________________
> > >> > Queue-developers mailing list 
> Que...@li...
> > >> > To unsubscribe, subscribe, or set options:
> > >> > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > >> >
> > >>
> > >> _______________________________________________
> > >> Queue-developers mailing list 
> Que...@li...
> > >> To unsubscribe, subscribe, or set options:
> > >> http://lists.sourceforge.net/lists/listinfo/queue-developers
> > >(See attached file: markd.vcf)
> > >--0__=882569D90024C2EF8f9e8a93df938690918c882569D90024C2EF
> > >Content-type: application/octet-stream; 
> > >	name="markd.vcf"
> > >Content-Disposition: attachment; filename="markd.vcf"
> > >Content-transfer-encoding: base64
> > >
> > 
> >YmVnaW46dmNhcmQgDQpuOkRlbm5pO01hcmsNCnRlbDtmYXg6KDQwOCkgNzE5L
> TQ4MDANCnRlb
> > Dt3
> > 
> >b3JrOig0MDgpIDcxOS00NzQyDQp4LW1vemlsbGEtaHRtbDpGQUxTRQ0Kb3JnO
> lJlZFN3aXRja
> > A0K
> > 
> >YWRyOjs7MTgxNSBNY0NhbmRsZXNzIERyaXZlO01pbHBpdGFzO0NBOzk1MDM1L
> TgwNDY7VVNBD
> > Qp2
> > 
> >ZXJzaW9uOjIuMQ0KZW1haWw7aW50ZXJuZXQ6bWFya2RAcmVkc3dpdGNoLmNvb
> Q0KdGl0bGU6U
> > 3Iu
> > 
> >IFVOSVggU3lzdGVtcyBBZG1pbmlzdHJhdG9yDQp4LW1vemlsbGEtY3B0OjsyN
> TE2MA0KZm46T
> > WFy
> > >ayBEZW5uaQ0KZW5kOnZjYXJkDQo=
> > >
> > >--0__=882569D90024C2EF8f9e8a93df938690918c882569D90024C2EF--
> > >
> > >
> > 
> > 
> > 
> > 
> > 
> > --__--__--
> > 
> > _______________________________________________
> > Queue-developers mailing list
> > Que...@li...
> > http://lists.sourceforge.net/lists/listinfo/queue-developers
> > 
> > 
> > End of Queue-developers Digest
> 
> _______________________________________________
> Queue-developers mailing list Que...@li...
> To unsubscribe, subscribe, or set options:
> http://lists.sourceforge.net/lists/listinfo/queue-developers
> 