Danial Howard wrote:
Also try putting the lp =xxx first before the tc=.c. I know, whatever parser lprng uses probably doesn't give a damn, but all the examples in the howto use this convention. Maybe it's that way just for readability sake.George Bell wrote:Danial Howard wrote:I have built LPRng and ifhp on an HP-UX 11i system. When I configure a queue like below, it prints fine if the job is postscript or pcl. If the job is a plain text file (/etc/profile), it has no carriage returns and runs off the rhs of the paper.
It shouldn't do this because ifhp should handle text files. I would check ifhp.conf. It is a very long conf file because it contains multiple possible settings for multiple printers. Find the one appropriate for your HP printer. It has the code for detecting the file type and applying the appropriate filter for that type. So for your hp printer look for the text converter entry, and follow the (paper) trail....
The problem is that I cannot use ifhp because the job hangs with error messages described elsewhere in this thread. There is some problem with the interaction of LPRng and ifhp or a simple filter.
.common:
:sd=/var/spool/lpd/%P
:mx=0:mc=0
cc_testlan_1:tc=.common:lp=hp2100tn%9100
When I change the printcap to use ifhp like this, the job just hangs in the queue.
cc_testlan_1:tc=.common:lp=hp2100tn%9100
:filter=/opt/lprng/libexec/filters/ifhp
:ifhp=model=hp2100
Make sure your que isn't clogged with unprintable jobs when your testing new ones. I always put the ifhp= line before the filter= line, if that makes any difference....
The queue is empty. I'll try reordering the lines to see if that helps.
Well, I can so far only come up with this idea. So it seems whenever you try to use a filter, *any* filter, the lp information seems to "get lost". Since filters can get a lot of their settings from environmental variables, I would check your environmental variables, to make sure they are not overriding the settings from the /etc/printcap. The runoffs on the page could also be explained by this. Some environmental variable might change the page size to A4 or ledger or something, causing the printer to think its printing on a larger sheet than is there.....I'm reading both HOWTO's. My printer supports Postscript, PCL, and raw text. I don't believe it requires ghostscript, though I do have that installed as a prerequisite of ifhp.The Lprng howto that comes with lprng and ifhp howto that comes with ifhp. What printer languages does your printer support? If it needs ghostscript then you need info on that too.
The problem remains when I disable the ifhp status option. I've turned on debug=3, and used lpstat with verbose output and am not sure what to look for.
The strange part is that ifhp works good on it's own. The source code has a README.TESTING file that I followed. I can call ifhp directly with an input file and it will send output directly to the printer. LPRng works without ifhp. Together, they are broken.
When building LPRng, I noticed a curious option on the cc comand line:
cc -DDEVFD0=\"DEVFD0\" ...
Is DEVFD0 representing stdin? Is this my problem?
Will someone help me? What info do you need?
That simple filter from the tutorial might provide some clues since it prints out the environmental variables.
Good luck
George
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
