Well, I am aware of what a queue in theoretical computer science is.
However, in real printign queues, one should be able to perform
non-queue operations on jobs, like moving items to the top (which is
possible and works in lprng) and removing a job from inside the queue
(which also works) and moving job from one queue to another (which does
not work... it waits until the job has proceeded to the top of the
queue, then moving it to another queue, making the move command useless
for moving a job from a congested queue to a less congested queue)

I am not sure if this is by design or a bug or has to do with me using a
filter... but filters are pretty common, so that shouldn't affect the
queue-managament?

Martin

On Sat, Dec 14, 2002 at 09:09:58AM +0100, [EMAIL PROTECTED] wrote:
> Hi Martin et al,
> 
> just try a 'lpc redo <printer> all, this will update the status for all
> printjobs, though I don't think there will be any 'real' actions like
> moving performed on jobs that are not active which is kind of obvious it's
> still a queue...
> 
> best regards
>       ~christoph
> 
> 
> -- 
> /*   Christoph Beyer     |   Office: Building 2b / 23     *\
>  *   DESY                |    Phone: 040-8998-2317        *
>  *   - IT -              |      Fax: 040-8998-4060        *
> \*   22603 Hamburg       |     http://www.desy.de         */
> 
> 
> On Fri, 13 Dec 2002, Martin Stolle wrote:
> 
> > Actually, lprng seems to be very limited in it's handling of print jobs.
> > It will never change anything for a print job before it reaches the top
> > of the queue. So you can transfer a job to a different queue, but that
> > only gets executed once the job would have printed on the original queue
> > anyways...
> >
> > This makes the move command more or less useless. (version: 3.8.15 )
> >
> > Martin Stolle
> >
> > On Fri, Dec 13, 2002 at 05:56:14PM -0500, Daniel E Singer wrote:
> > > On Fri, 13 Dec 2002, Jose wrote:
> > >
> > >  > In the following situation , I try to use "lpc move" :
> > >  > a big job (9000 pages) is running on printer1 causing
> > >  > all others jobs on printer1 to wait his end.
> > >  > I use the command:
> > >  > "lpc move printer1 jobid printer2"
> > >  >
> > >  > The command lpq -Pprinter1 tell me that the job has been
> > >  > moved to printer2, but nothing print on printer2
> > >  > What is my error ?
> > >  > We use LPRng-3.6.24 on a Redhat 7.0
> > >
> > > Maybe try:
> > >
> > >   lpc move printer1@printserver jobid printer2@printserver
> > >
> > > this assumes that your `printserver' is some other machine (substitute
> > > its host name in the above command).
> > >
> > > I don't have any other suggestions, if that doesn't work.
> > >
> > > --
> > > Daniel E. Singer, System Administrator
> > > Dept. of Computer Science, Duke University, Durham NC 27708 USA
> > >
> > >
> > > -----------------------------------------------------------------------------
> > > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> > > The address you post from MUST be your subscription address
> > >
> > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> > > or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> > > to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> > > with:                           | example:
> > > subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> > > unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
> > >
> > > If you have major problems,  send email to [EMAIL PROTECTED] with the word
> > > LPRNGLIST in the SUBJECT line.
> > > -----------------------------------------------------------------------------
> >
> > -----------------------------------------------------------------------------
> > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> > The address you post from MUST be your subscription address
> >
> > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> > or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> > to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> > with:                           | example:
> > subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> > unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
> >
> > If you have major problems,  send email to [EMAIL PROTECTED] with the word
> > LPRNGLIST in the SUBJECT line.
> > -----------------------------------------------------------------------------
> >
> 
> 
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
> 
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> with:                           | example:
> subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
> 
> If you have major problems,  send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to