HP3000-L Archives

January 1996, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Joerger <[log in to unmask]>
Reply To:
John Joerger <[log in to unmask]>
Date:
Sun, 21 Jan 1996 17:33:28 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
On Thu, 18 Jan 1996, Larry Byler wrote:
> (Sorry to be chiming in so late, but no one has mentioned this aspect of the
> issue).  I tend to agree with Gavin that moving an executing job to a
> different (hopefully more appropriate) queue is more intuitively obvious to
> an operator and simpler conceptually than all the other workarounds various
> people have suggested.  But what do you do if the target queue is already
> at limit?  Does the move fail?  Do you ignore the target queue limit (except
> to hold off newly introduced jobs from executing until enough jobs log off)?
> Does the job whose queue you are changing suspend until it is within queue
> limit?  Does an existing job in the target queue suspend instead?  Which one?
 
I would vote for rejecting the queue reassignment.  This seems the easiest
to implement and one an Operator should be able to effectively deal with.
 
Regards,
 
--- John Joerger  ([log in to unmask])  ---  Press-Telegram (Long Beach)

ATOM RSS1 RSS2