Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Feb 2000 12:44:24 +0000
From:      Robin Melville <robmel@innotts.co.uk>
To:        "Charles N. Owens" <owensc@enc.edu>, Nik Clayton <nik@FreeBSD.ORG>
Cc:        questions@FreeBSD.ORG, stable@FreeBSD.ORG
Subject:   Re: FreeBSD 3.4, Samba, HP LaserJet 5N, delays, reboots
Message-ID:  <v04220800b4d0484ba8cc@[172.16.17.20]>
In-Reply-To: <38A48A9C.A3BB2D75@enc.edu>
References:  <20000211123416.A92889@catkin.nothing-going-on.org> <38A48A9C.A3BB2D75@enc.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

>Nik Clayton wrote:
>
>[...snip] As soon as there's more than one print job
>  > in the queue (either 2 or more jobs from one machine, or 2 or more jobs
>  > from multiple machines) the applications that are printing on each host
>  > hang (hourglass, unresponsive to input) until the print jobs have gone
>  > through.  The Windows 98 hosts have the most up to date drivers from HP.

At 5:18 pm -0500 11/2/00, Charles N. Owens wrote:
>[...snip]
>While a job is being sent, however, the single-TCP connection limitation means
>that it cannot respond to lpq queries!!  Very bogus!
>
>You can see this for yourself... lpq works just fine when there are 
>no jobs in the
>queue.  Shove a bunch of jobs in the queue and try lpq again... it 
>will print out
>the list of jobs in the local server queue but as it then tries to query the
>printer it gets no response and will just sit there waiting.
>
>As long as your Windows users never use the printer control panel to check job
>status things should be generally fine... If they do use it and 
>there are no jobs
>currently in that Samba (lpd) queue then every thing will still seem fine.  If
>however the print status window is opened while there _are_ jobs in the queue
>they'll get this terrible hanging system problem.   When this happens samba is
>calling lpq, which of course hangs because it gets no answer from the printer.

We've seen this with other lame in-printer lpd emulations, Lexmarks 
are as bad. A simple fix is to hack as follows. A flag in 
/etc/printcap would be a more complete
solution.

----------------
--- /usr/src/usr.sbin/lpr/common_source/displayq.c      Sat Sep 11 
11:25:16 1999
+++ /usr/src/usr.sbin/lpr/common_source/displayq.c+     Wed Feb 16 
12:38:20 2000
@@ -214,6 +214,12 @@
                 return;
         }

+       /* kludge to stop propagation of lpq requests hanging on broken
+          printer lpd emulations. NB. stops *all* propagation from this
+          lpd server.
+       */
+       return;
+
         /*
          * Print foreign queue
          * Note that a file in transit may show up in either queue.
-----------------

Best wishes

Robin.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04220800b4d0484ba8cc>