HP3000-L Archives

January 1996, Week 2

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:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Fri, 12 Jan 1996 23:21:46 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On Fri, 12 Jan 1996 23:24:14 GMT Steve Cooper said:
>In all of this great discussion on Multiple Job Queues, I have not
>seen specific reference to one special type of job.  It may be obvious
>and it may not have any special requirements, but I thought I'd
>mention it, just for the sake of completeness.
>Every system seems to have some number of jobs that are supposed to be
>running ALL of the time.  These are equivalent to what UNIX might call
>"daemons".
 
I'm hoping my post on this was sent out OK; Gavin has replied to it so I
presume it is, maybe Steve is just as backlogged on mail as I am :-)  But
I agree 100%, it was my #1 need.
 
The other issue Gavin and I disagree on, in a nutshell, is how can you
run a job RIGHT NOW.  Gavin suggests moving an active job in the queue in
question to another queue, I suggest a HOT queue with an implicit ;HIPRI
that could be restricted to OP/SM users.  I will address that further in
a follow-up to his reply; meanwhile I'm reading ahead to make sure that I
don't duplicate myself again :-)
 
Jeff Kell <[log in to unmask]>
 
PS - The "daemon" queue idea is related to a similar enhancement request
at the last IPROF for a "system-adopted process", same idea, but perhaps
a more traditional implementation as a special job queue (IMHO).

ATOM RSS1 RSS2