Bug 21041

Summary: Printtool won't set up network printer
Product: [Retired] Red Hat Linux Reporter: Need Real Name <budden>
Component: printtoolAssignee: Tim Waugh <twaugh>
Status: CLOSED NOTABUG QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: buysse
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-11-05 14:29:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2000-11-18 00:56:03 UTC 
I use printtool to set up to a Laserjet 4000 which has ethernet interface
and currently assigned IP address of 131.120.179.37.  When I close out of
printtool, I get the following fragment in /etc/printcap.  If I understand
what's going on, I _should_ be getting the IP address in the lp= line
instead of /dev/null.  

The symptoms I get are consistent with files getting sent to /dev/null --
lp says it sent the job and there's nothing in the queue.

##PRINTTOOL3## DIRECT laserjet 300x300 letter {} LaserJet Default 1
lp:\
	:sd=/var/spool/lpd/lp:\
	:mx#0:\
	:if=/var/spool/lpd/lp/filter:\
	:af=/var/spool/lpd/lp/acct:\
	:lp=/dev/null:\
	:sh:

Printtool v.3.54 as bundled in RH7.0.  Installed on i696 laptop.  Ethernet
works fine (using it to submit this).
Comment 1 Crutcher Dunnavant 2001-04-12 19:46:02 UTC 
well, you see, the filter is actuall supposed to do delivery in this case, so
any out put from the filter is going bye-bye.

can you check to see if the file:

	/usr/lib/rhs/rhs-printfilters/directprint

exists? Its the bit that is supposed to do jet direct printing.

also, try setting it up as an lpd spool with that IP, the printer may support it.
Comment 2 Tim Waugh 2002-01-10 13:44:38 UTC 
Is this bug still current?
Comment 3 Tim Waugh 2003-11-05 14:29:32 UTC 
No response; closing.