It is the same problem we and quite a few other people are having.
If you have the HP 8150 printers there is a new firmware upgrade for them
that might solve the problem. Otherwise I really don't know what to tell
you.


On Fri, 12 Mar 2004, Toby Blake wrote:

> Hmmm, going back to this problem we see when print queues get large
> and the print server load is extremely high, can anyone explain why
> this happens (for technical info see previous messages in this thread
> - I won't repost it all here).
>
> We run student labs and times like today, where assignments are due
> in, result in printers running extremely slowly, but the delay is
> between the jobs (i.e. the printer is doing nothing between each
> printed job, the delay is at the server side) and is definitely
> related to the size of the queue, e.g.
>
> [kant]toby: lpq -s -Pat3
> [EMAIL PROTECTED] 49 jobs
> [kant]toby: lpq -s -Pat8
> [EMAIL PROTECTED] 36 jobs
> [kant]toby:
>
> [dickinson]lp: uptime
>   4:03pm  up 119 days, 22:49,  1 user,  load average: 9.64, 9.18, 7.20
>
> The delay between jobs right now, with this load and these queues is
> 14 minutes.  This delay occurs here:
>
> finished '[EMAIL PROTECTED]', status 'JSUCC' at 2004-03-12-15:42:49.171 ## [EMAIL 
> PROTECTED] number=712 process=16602
> waiting for subserver to exit at 2004-03-12-15:56:16.463 ## A=<NULL> number=0 
> process=14349
> subserver pid 16602 exit status 'JSUCC' at 2004-03-12-15:56:16.463 ## A=<NULL> 
> number=0 process=14349
>
> .... so after the job has successfully printed, it waits for an lpd
> process to exit, which takes 14 minutes.
>
> What are the lpd processes doing in the time that chews up so much CPU
> - this is very much related to the size of the queue - if I removed
> half the jobs in the queue, the delay between jobs would significantly
> decrease (I know this because I've tried it).
>
> Note that our print servers are currently running RH7.1 - I'll be
> upgrading them to RH9 soon, although I'm not sure this will have any
> effect.  They're running either LPRng 3.8.10 or 3.8.21 -  this happens
> with both.
>
> I'd appreciate any help or advice as to what we can do to stop this
> happening - note again that it only happens when there are a lot of
> print jobs in the queue, so 99.9% of the time we have no problems
> whatsoever - I have watched the load increase and the delay between
> jobs increase as more are added to the queue.
>
> Many thanks in advance
> Toby Blake
> University of Edinburgh
>
>
> -----------------------------------------------------------------------------
> 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