Here my 2 cents worth on these printacp entires: :lp=: --> I would say this entry is spurious, since the printer is defined with the "rp" and "rm" entires.
":rm=barricade" --> this is the IP Address of the port to which the printer is attached. I entered this in the /etc/hosts, and it translates to "192.168.123.254", the address of the broadband router. ":rp=lp" --> this is the printer on the barricade broadband router. The whole printer would be "lp=lp@barricade", in the "new" notation. In the second entry: ":lp=/dev/null" --> I have seen this entry very often in this system, it gets generated by both "SETUP" that comes with apsfilter, and the graphic thingees that the distribution supplies to administer printers. The thing that throws me completely, is that this printcap printer definition works with ONE printer, but ONLY with one. Lo and behold, all other printouts send their output to /dev/null. I guees I was surprised by the wrong thing: not that the first printer printed, but that they DIDN'T!!! I will work through the web pages you indicated to me, and get a simple, streamlined printcap out of it, and let you know how it goes. Thanks for everything, Helmut Joel Hammer schrieb: > Just some comments here. I do not know what printers > these are for but: > > remote|lp1|barricade-lp-remote|barricade lp:\ > :lp=:\ <--WHAT is this print device???? > :rm=barricade:\ <--IS THE YOUR PRINTER CONTROL DEVICE? > :rp=lp:\ <--WHAT IS THIS PRINT QUEUE? > :sd=/var/spool/lpd/barricade-lp-remote:\ > :lf=/var/spool/lpd/barricade-lp-remote/log:\ > :af=/var/spool/lpd/barricade-lp-remote/acct:\ > :ar:bk:mx#0:\ > :tr=:cl:sh: > > low-ascii|lp2|y2prn_low.upp--ascii-low|y2prn_low.upp > ascii:\ > :lp=/dev/null:\ <----ALL THESE JOBS ARE GOING TO THE > BYTE BUCKET > :sd=/var/spool/lpd/y2prn_low.upp--ascii-low:\ > :lf=/var/spool/lpd/y2prn_low.upp--ascii-low/log:\ > :af=/var/spool/lpd/y2prn_low.upp--ascii-low/acct:\ > :if=/var/lib/apsfilter/bin/y2prn_low.upp--ascii-low:\ > :la@:mx#0:\ > :tr=:cl:sh: > > According to this, lp2 is sending all its jobs to the > device /dev/null, > which is oblivion. Unless the apsfilter is magically > sending your jobs to > the correct place, but, it doesn't sound like it. > Why don't you send all your jobs to barricade, too, > whatever that is. > Joel > > > -------------------------------------------------------- > --------------------- > 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. > -------------------------------------------------------- > --------------------- > > ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
