Hi Joel, the "about 10 printers" are OK, they are simply the standard raw & ascii printers plus the auto printer. They are automatically generated by apsfilter's setup, as well as by the graphical tools I could use to define the printers.
I have tried your suggestion, by manually copying the "auto" printer, but it seems to be a problem with lpd, in that the second printer defined to print on "/dev/null" doesn't reach the printer "lp@barricade". The printouts simply disappear. That was the reason I tried the funnelling queue, which I got as a tip from an old "plp" help page. As i have unterstood it, the chain of printing goes from printcap to apsfilter to device. Printacp routes to the appropriate apsfilter using the device name for driver, resolution, page size, color etc. Apsfilter uses ghostscript to generate an appropriately formated file and routes it, using the printcap printer queue, to the printing device (in this case the remote queue lp@barricade), which then produces the printout. In the first printcap, the printouts get lost after ghost script has preprocessed the file; seems to me, that ghsotscript doesn't route to "lp@barricade" successfully. The plp help page, regarding funnelling, said that lpd would find the device "lp@barricade" to be busy when printeing from a second or later printer, as the first printer ist tied to this physical queue, and will "lose" the printout. That is why my question, if one can not tell the "lp@barricade" printer that it is SHARED. Or maybe the individual queues need such an entry. In the second printcap, I route the printouts from all printers to an intermediate queue; this is then the only queue that prints onto the physical device "lp@barricade". In this case, the printouts, correctly filtered with the resolution I expect, arrive at the printer & get printed. They disappear from the "funnel" printer's spool file OK. However, this "printed" status does not get back to the originating queues. The first printout says as status that it is "still trying". The other printouts say "failed...". After a timeout period, the first printout gets aborted (ONLY in the spooler queue, the printout is long time printed successfully in all cases) because of the tiemout The spool files then remain forever in the spoolers of the corresponding printers. I wish it WAS as straightforward as you suggested: but beieve me, I have tried that as my first shot. Because of the lack of any kind of success in my attempts, I have cleared the board of all the confused failed solutions and present only those positions that I feel represent a "standard" situation. Any hope with the idea of getting the "lp@barricade" queue to be shared by lpd with other printers? I guess this would solve the problem with the funnelling queue, it also looks like the queue is marked as "busy" in some way, probably from the CORRECTLY routed jobs. Joel Hammer schrieb: > This printcap file has entries for about 10 printers. Why > don't you configure > a printcap file for just one printer, either manually or > with whatever graphical thingee > you are using, then duplicate (manually) the working > queue, subsituting > approriately as needed? > After you do that, run checkpc -f, and you should be ok. > 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. -----------------------------------------------------------------------------
