On Wed, 22 Jan 2003, Henrik Edlund wrote:
HE> On Sat, 18 Jan 2003 [EMAIL PROTECTED] wrote:
HE>
HE> > do you refer to 3.8.19 ?
HE> > i didnt see the problem. please do the following test:
HE> > 1. create a test queue and redirect to to a file
HE>
HE> As I wrote it works as it should if I print to a file.
HE>
HE> What is run when a third job arrives so that the second is flushed
HE> out as well? Is this something I can configure. I tried setting
HE> the force_poll option but that didn't help. What other options is
HE> there that affect this?
I tracked this down to the queue in which this happened was a
slave queue and in lpd_jobs.c it says:
* Note: if we spool something to a slave queue, then we need to start
* the master server to make the slave printer work.
So the first job got printed but the second just stayed there
until a third job arrived and the queue "got activated" again.
--
"Nope, I'm just an ordinary guy with nothing to lose."
-- Lester Burnham, "American Beauty"
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
