Bug 5609 - lpd(8) cannot send long files to HP's JetDirect interface
Summary: lpd(8) cannot send long files to HP's JetDirect interface
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1998-01-31 14:40 UTC by conrad
Modified: 2018-02-02 20:17 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description conrad 1998-01-31 14:40:01 UTC
We're using a HP LaseJet 5m with JetDirect Interface with low memory.
(The printer's name is avzp02) The printcap entry is
:lf=/var/log/lpd-errs:lp=:mx#0:rm=avzp02:rp=raw:sd=/var/spool/output/lp8:

When printing a file of more than about one megabyte, only the beginning of
the file is printed and the job stays as unprinted in the queue
lpc reports: no daemon present.
The file is never printed again unless someone sends a new file with
lpr. Then again the first part is printed and so on....

Fix: 

Don't know... send it to a DEC OSF Box first - DEC's lpd has no problems
How-To-Repeat: just do it :-)
Comment 1 conrad 2000-03-29 14:53:14 UTC
Hi,

an email from Trev Roydhouse <trev@sentry.org> just reminded me that this
is still open and still bothers people...

The default timeout for the ct entry is 120 secs which is too short for
most LaserJet printers with network interfaces.

I suggest to set it to something like 6000 (:ct#6000:)

How about setting this in

/usr/src/usr.sbin/lpr/common_source/lp.local.h (line 52)
/usr/src/usr.sbin/lpr/lpr/printcap.5 (line 81)

best regards
	Jan

-- 
Physikalisches Institut der Universitaet Bonn
Nussallee 12
D-53115 Bonn
GERMANY
Comment 2 trev 2000-04-08 08:52:24 UTC
Workaround:

We solved the problem by specifying :ct#6000: in the printcap entries.
Its nothing but a timeout problem because the LaserJet network
interfaces
just die while printing... [from Jan Conrad]
Comment 3 Garance A Drosehn freebsd_committer freebsd_triage 2001-05-25 00:47:28 UTC
Responsible Changed
From-To: freebsd-bugs->gad

I intend to change something to address this (probably both change the 
default, and include a hint somewhere so people are more likely to know 
what to try when they see this problem come up).
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:39 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 5 Eugene Grosbein freebsd_committer freebsd_triage 2018-02-02 20:17:42 UTC
That was local problem solved with corresponding /etc/printcap configuration.