On Sat, Apr 24, 2004 at 06:34:40PM +1000, Craig Small wrote:
> 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

It appears to be a BUG!

When a job is 'moved' to a new queue the new job 'control file'
does not have appear to have the 'move' field in the 'control file' cleared.

I will check into this and fix this up.

Symptoms:  if you look at the 'read' and 'write' calls, you will find a 'move=...'
appearing in the values read or written.  This should not be the case if the
control file is for a new job or when moved to a new queue.


27626 open("/var/spool/lpd/cc-hp8150/temp00CorAtu", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 
0600) = 6
27626 fchmod(6, 0600)                   = 0
27626 stat64("/var/spool/lpd/cc-hp8150/temp00CorAtu", {st_mode=S_IFREG|0600, 
st_size=0, ...}) = 0
27626 write(6, "[EMAIL PROTECTED]:16:32.536\ndatafile_co
unt=1\ndone_time=0x0\nerror_time=0x0\nfile_hostname=random.ams.attingo.nl\nH=random.ams.attingo.nl\nheld=0x0\nhf_name=hfA13
7\nhfdatafiles=copies=0x1\2dftransfername=dfA137random.ams.attingo.nl\2format=f\2size=163434\1\nhold_class=0x0\nhold_time=0
x0\nJ=iws-d-1-2: 
http://www.cybertravelnetwork.com/cs/1.htm\njob_time=0x407fdcd1\njob_time_usec=0x8487d\nmove=cc-hp8150\nnu
                                                                                       
                  ^^^^^^^^^^^^^^
mber=137\nP=nobody\nprintable=0x0\npriority=A\npriority_time=0x0\nprstatus=moved->cc-hp8150\nQ=iwsqueue\nremotehost=localho
st\nremoteport=0x0\nremove_time=0x0\nserver=27626\nsize=163434\nstart_time=0x407fdcd1\nunixsocket=0x1\nupdate_time=2004-04-
16-15:17:05.588\n", 702) = 702
27626 close(6)                          = 0
27626 rename("/var/spool/lpd/cc-hp8150/temp00CorAtu", "hfA137") = 0
                            ^^^^^^^^^^

-- 
Patrick Powell                 Astart Technologies
[EMAIL PROTECTED]            6741 Convoy Court
Network and System             San Diego, CA 92111
  Consulting                   858-874-6543 FAX 858-751-2435
LPRng - Print Spooler (http://www.lprng.com)

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