Hi there,
Couldn't this be that your server is short on memory and spend all
its time swapping memory ?
What does the 'top' command says wrt memory usage ?
Definitely not memory - there's plenty free.
Toby
-
YOU
Hi there,
What kind of chooser are you running? Old versions of LPRng would
run the chooser script/program once for every job in the queue,
every time it checked. This meant the longer the queue, the longer
the load, the longer the time to run the chooser, the more the queue
growing and so
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.
Is it this problem? I'd thought that was a printer side problem,
which
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
Hi,
On Fri, Mar 12, 2004 at 04:12:07PM +, Toby Blake wrote:
... 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
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
What kind of chooser are you running? Old versions of LPRng would run the
chooser script/program once for every job in the queue, every time it
checked. This meant the longer the queue, the longer the load, the longer
the time to run the chooser, the more the queue growing and so on..
Running
50% of CPU used by lpd certainly looks like a problem to me. This
is definitely not typical. Are you also seeing a lot of disk
activity?
No, nothing unusual.
Have you posted your printcap yet?
Hmm, difficult to do as it gets printcap data out of ldap. Here's the
printcap data for the one
50% of CPU used by lpd certainly looks like a problem to me. This is
definitely not typical. Are you also seeing a lot of disk activity?
Have you posted your printcap yet?
Phillip Griffith (803) 952-8776
Information Technology Department
Westinghouse Savannah River Company
[EMAIL PROTECTED]
Hi again,
What is causing the load such that the main lpd process is so busy?
Does the size of the queues affect how much lpd does? This machine
is only serving 8 printers and when the load has been really high,
it has only ever been one or two printers with large queues - the
other queues
Note that I'm running LPRng-3.8.10 - I haven't had a chance to test
newer versions properly, but will do so soon.
I've just looked through the CHANGES file and see that a fair bit of
stuff related to this was changed in 3.8.20. I'll upgrade as soon as
I can and see if this makes a difference.
Hi,
Can I just ask a further question about this
What is causing the load such that the main lpd process is so busy?
Does the size of the queues affect how much lpd does? This machine is
only serving 8 printers and when the load has been really high, it has
only ever been one or two
Hi there,
Thanks for the reply.
These processes are 'zombies' waiting for the main LPD process to
harvest (wait) for them. The LPD code is waiting in a select
loop for either a process to exit or for a connection.
Setup_waitpid_break();
errno = 0;
fd_available =
From [EMAIL PROTECTED] Mon Dec 15 03:36:49 2003
Date: Mon, 15 Dec 2003 10:46:45 + (GMT)
From: Toby Blake [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: LPRng: lengthy delay between one job finishing and another one
starting
If you are using your own filters, then make sure you
If you are using your own filters, then make sure you close
the STDOUT/STDIN, etc., and make sure you exit.
I'm almost 100% certain that the problem is *not* related to our
filters. As you can see below, the psif filter happily finishes at
15:27:59, however there is a further delay of 7
From [EMAIL PROTECTED] Thu Dec 4 08:57:58 2003
Date: Thu, 4 Dec 2003 16:12:49 + (GMT)
From: Toby Blake [EMAIL PROTECTED]
To: John Perkins [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: LPRng: lengthy delay between one job finishing and another one
starting
Hi there,
Firstly
Hi there,
Firstly, thanks for your reply.
Check lpq -L between jobs and find out if ifhp or lpd is causing
the delay. If you have a long waitend delay or high waitend repeat
(number of times to keep polling the printer for pagecount or status
until the response stablizes), you will see such
I didn't realize you were using your own filter for this...
Yep, I mentioned it in my original email, as people tend to assume
we're using ifhp.
Can you run your filter on the command line without such delays?
Usually, yes. The trouble is that I can't do any testing now, as I
can obviously
18 matches
Mail list logo
