Bug 18683

Summary: Incorrect printcap generation for network printer
Product: [Retired] Red Hat Linux Reporter: gregory.hosler
Component: printtoolAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED DEFERRED QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: dr
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: 2000-10-09 10:08:01 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 gregory.hosler 2000-10-09 08:50:35 UTC
I have a problem that used to work on earlier RH systems. 

I have a remote print queue on a HP-UX system.

I run printtool.

I click [Add] -> <> Remote Unix (lpd) Queue, add my remote hostname and
remote
queue name.

The generated /etc/printcap looks like this:

##PRINTTOOL3## REMOTE 
ps:\
	:sd=/var/spool/lpd/lp:\
	:mx#0:\
	:sh:\
	:rm=hawaii:\
	:rp=lp:\
	:lpd_bounce=true:

The last line (:lpd_bounce=true:) will cause printing to fail. i.e.
when I print something/anything, The following displays
in/var/log/messages:

Oct  9 16:29:50 amnesia (Worker - Remote)[2443]: ps: Remote_job: fstatb
failed - Bad file descriptor
Oct  9 16:29:50 amnesia (Worker - Remote)[2443]: ps: Remote_job: close(5)
failed - Bad file descriptor

I must manually remove the lpd_bounce line - note that setting
:lpd_bounce=false:
also works - the "true" setting is definately wrong.

I suspect that printtool is generating the default printcat, and this
should be changed.

-Greg

Comment 1 Crutcher Dunnavant 2000-10-11 16:04:37 UTC
Garh, this is yet another "How do most people expect printtool to behave" issue.

The answer is this:
lpd_bouce=true tells the system to filter requests locally, before sending them.
This way, you can easily print to postscript only printers, because the format
gets changed locally, and postscript gets sent to the printer. For most people,
this is a good thing.

However, apparently printtool doesn't notice if you don't set a filter (which
you didn't), so LPRng tries to filter locally, and sends some wierdness on to
the remote queue (because you told it to filter, using no filter, so ...).

So, the in-printtool answer is: select a print filter for the remote queue.
Sorry.

I will put this on the pile of printtool changes that need to be made.