Bug 17774 - Direct to port printer does not work
Summary: Direct to port printer does not work
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: printtool   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact:
URL: http://www.linuxprinting.org/howto/ne...
Depends On:
TreeView+ depends on / blocked
Reported: 2000-09-21 16:04 UTC by ingvar
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-09-23 22:39:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description ingvar 2000-09-21 16:04:26 UTC
Running Red Hat 6.2 with kernel 2.2.16-3, and printtool-3.44-1.
Want to use an old HP LaserJet III si with PostScript and hooked directly
to the network. This printer has no built-in lpd daemon, but listens to
port 9100 as described in the Printing Howto at
http://www.linuxprinting.org/howto/network.html#NETWORKED-PRINTERS , in
section 11.5.1. 

For testing, the perl script on that page works (with a little hacking, one
has to remove the use of the variables $dpi300 and $dosCr ).

Using printtool, I select "Add", "Direct to port printer", and fill in the
fields "Names" (snorre), "Spool Directory" (/var/spool/lpd/snorre), "File
Limit" (0), "Hostname of Printer" (snorre), "Port number" (9100), "Input
Filter" (*auto* - PostScript with 300x300 and a4) and "Suppress Headers"

The printer is correctly set up, answers on `telnet snorre 9100` , and
sending PostScript code to this port with the mentioned perl script prints
wonderfully. But the lpd daemon, set up (and restarted, of course) with the
settings mentioned over, does not seem to send anything at all. When
spooling something with lpr -Psnorre something.ps , it just disappears.
Nothing in the queue, nothing in /var/log/messages. Adding a
:lf=/var/log/printlog:\ line to the printcap reveals absolutely nothing in
the print log either. 

It may be possible to hack the perl script on the page to be used as a
filter, but I think it would be a better solution to make printtool behave
as one would expect.

Ingvar Hagelund

Comment 1 Need Real Name 2000-09-23 04:06:54 UTC
/usr/lib/rhs/rhs-printfilters/directprint is missing. 

* Wed Apr 19 2000 Bill Nottingham <notting@redhat.com>
 - add directprint file. *oops*

Comment 2 ingvar 2000-09-23 22:01:32 UTC
Just for the record: Will a fix come as an updated rpm? Will it be in RedHat


Comment 3 Need Real Name 2000-09-23 22:39:23 UTC
/usr/lib/rhs/rhs-printfilters/directprint is missing. 

* Wed Apr 19 2000 Bill Nottingham <notting@redhat.com>
 - add directprint file. *oops*

Note You need to log in before you can comment on or make changes to this bug.