I just set up LPRng on one of my Linux servers. The mixture of junk I had on it
before -- cups, alternative software, and a bunch of weird PrintConf extensions that
Red Hat thought I needed -- did not allow me to modify my "send_try" in my printcap.
LPRng saved my ever living butt.
In the process of installing LPRng, I do believe I have uncovered several
bugs. This is my configuration:
Red Hat 9 (upgraded from RH 6.2 and RH 7.2)
ghostscript-7.05.5-0.i386.rpm
LPRng-3.8.19-3.1.i386.rpm
gimp-print-4.2.5-2.i386.rpm
LPRngTool-1.3.2-1.i386.rpm
ifhp-3.5.6-1.i386.rpmFirst some background. When I am addressing a Jet Direct print server or similar, I have traditionally addressed it in /etc/printcap as such:
:rm=192.168.255.7
:rp=raw1I seems that LPRng has changed this to
:[EMAIL PROTECTED]
It sticks "rm", "rp", and the port number all into "lp". This I can live with, EXCEPT:
BUG 1: the manual page for printcap still reflects the old "rm/rp" method and makes
no mention of the new combined "lp" method. For those of us who like to read
the directions, this is not fair play
BUG 2: the manual page for printcap, in the sections that defines the command
can only be viewed in an xterm properly if the xterm is maximized
BUG 3: the new super "lp" method does not work. /etc/printcap must be hand edited to the following: # :rm=192.168.255.7 # :[EMAIL PROTECTED] :lp=192.168.255.7%9100 :rp=raw1
Note that you must
A) use an "lp", "rp" pair, and
B) remove the queue name and "@" symbol ("raw1@") from "lp".BUG 4: if you edit the queue with LPRngTool, LPRngTool will change the "lp",
"rp" pair back to the super "lp" method. Meaning you have to remember to hand
edit the "lp", "rp" pair back into /etc/printcap.
BUG 5: Speaking of LPRngTool, I need to be able to specify the print queue
name ("rp") when setting up a printer for LPR/LPD. LPRngTool removes this
option when setting up this kind of printer. This creates a real mess when setting
up a Jet Direct 500x with three queues names (raw1, raw2, and raw3) for
each of its three parallel ports.
BUG 6: The manual pages for LPRng, use LPRng as part of their name
("lpr.LPRng.1.gz"). (So I know I have the right pages complained about
in bugs 1 & 2 and not a leftover CUPS page.) It is a total pain in the neck
to address them as "man lpr.LPRng". (I spent 20 minutes creating symbolic
links to all of them. Not having the directions at my touch is a REAL
annoyance.)
Many thanks, --Tony [EMAIL PROTECTED]
-- ------------------------- I Fish. Therefore, I am. -------------------------
----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
