On Fri, 23 Jan 2004, Anthony Ewell wrote:
> Hi All,
>
> In the process of installing LPRng, I do believe I have uncovered
> several
> bugs. This is my configuration:
<snip>
> First 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=raw1
>
> I 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:
Well, the real problem here to my eyes is that you are ending up with a
[EMAIL PROTECTED] You use the first or the last (like "before
and after" on Wheel of Fortune ;)), but I don't think altogether that that
is proper syntax. If you are doing it, it's bad syntax (though you seem to
be indicating the software is doing it -- but read below...)
<snip>
> 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.
OK, if I'm right about the above portion (I'm pretty certain I am as I've
been doing this awhile ;)), you've got this all hosed. Like I said above,
you pick the proper port (ie 9100, 9101, etc.) OR you pick a queue and the
port used is 515 (LPR). AFAIK, both is bad syntax. My personal
recommendation is:
:[EMAIL PROTECTED]
...this should do what you want. If you are using 9100, you should omit
the queue name as each port will be defined as a particular queue. Again,
this is only as I understand it, but I believe I answered this question
already on the list in the past and others concurred with my
understanding.
Now, a caveat here that I've noticed is if you are using ifhp as your
filter (you have not indicated either way), you will most likely want:
:lp=/dev/null
:[EMAIL PROTECTED]
...something about the addr already being open while ifhp tries to access
it -- but this does not seem like your problem.
Bottom line: if rm/rp does not work and inserts 9100 at the end without
you suggesting it (I don't believe it did last time I tried it), that is a
bug. If you are manually using a queue name and port name, I think it's
pilot error.
HTH!
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin
|$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
