From owner-freebsd-hackers Tue Mar 4 11: 8:44 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4361F37B401 for ; Tue, 4 Mar 2003 11:08:43 -0800 (PST) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6445A43F3F for ; Tue, 4 Mar 2003 11:08:42 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.12.7/8.12.7) with ESMTP id h24J8eqX014501; Tue, 4 Mar 2003 14:08:41 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <5.2.0.9.2.20030303112107.00bc55d8@mail.servplex.com> References: <5.2.0.9.2.20030303112107.00bc55d8@mail.servplex.com> Date: Tue, 4 Mar 2003 14:08:40 -0500 To: Peter Elsner , freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: lpc problem with LinkSys print servers Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:31 AM -0600 3/3/03, Peter Elsner wrote: >This particular printer is a high load printer, printing about >50 to 70 pages at a time. Occasionally, the printer just stops >while printing. > >We have to force a 'lpc restart lsjd1p2' command several times >to get the printer to restart again. You will sometimes have better luck if you 'lpc abort' the queue, wait a few seconds, and then 'lpc start' it. Of course, that doesn't solve the actual problem... >I believe that lpr/lpd is not resetting after receiving a >Busy/Ready (or Nack/Ack) signal. > >Has anyone else seen this problem before? I have not heard of it. I'd like to see some actual proof of what is happening (like a tcpdump) before assuming that it's lpd's fault. Mind you, I'm quite willing to believe it's lpd's fault, but I can't very well look into the problem unless I know what sequence of packets is causing it. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message