A Debian user has found that lprng goes into some tight loop and eats
his CPU.

I really cannot see what the problem is Patrick so I'm asking you for
your assistance.

  - Craig

----- Forwarded message from Wichert Akkerman <[EMAIL PROTECTED]> -----
Package: lprng
Version: 3.8.26-1
Severity: grave

lpd on my printserver goes insane occasionaly, apparently while
processing a printjob. Symptoms are one or more lpd processes consuming
all CPU while scanning over a print spool. I caught a strace of this
which is availably at http://www.wiggy.net/tmp/lpd.bug.bz2 .

The configuration is simple: I have two printqueues: a bouncequeue
going directly to a printer and a permanently stopped queue on which
jobs are submitted and then moved on demand to the other queue.

This setup worked fine with previous versions of lprng.

Wichert.

-- 
Wichert Akkerman <[EMAIL PROTECTED]>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.




----- End forwarded message -----

-- 
Craig Small      GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/   MIEE         Debian developer
csmall at : enc.com.au                      ieee.org           debian.org

-----------------------------------------------------------------------------
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