On Tue, 5 Mar 2002, Patrick Powell wrote:
> Find the port that the copier listens on for TCP/IP stuff.
> It's documented somewhere.
>
> Say its port 9100.
>
> Then use the printcap:
>
> lp:
> :lp=ip.address%9100
> ....
>
>
> and LPRng will open a connection to the port.
Thank you very much for your response. As I mentioned in my original
post (below), the copier/printer runs an internal LPD spooler, so it
listens on port 515 and only accepts jobs this way.
If I send a job directly to the printer with:
lpr -Pprint@pr167 file.ps
it will print. But we would like to take advantage of LPRng's
filtering and job translation capabilities. Therefore, we would like
to send the job to the LPRng print server, have the job processed,
then sent on to the LPD spooler on the copier/printer.
I'm reading thru docs., and trying different things, but so far it's
not working. Sometimes I get printed PJL and Postscript. Sometimes
it seems to queue and process, but nothing comes out. Bytheway, the
Canon copier/printer supports jobs in PCL and Postscript.
Should I send more info, such as printcap and lpq output? If this
gets working, I promise I'll send the config info back to the list!
> > We have a Solaris-8 print server, all of our Unix boxes forward print
> > jobs to the server for processing, and PC's print to the print server
> > via Samba. Most of our printers are HP's with network cards.
> >
> > The Canon runs its own lpd server, so I can send a print job (eg,
> > Postscript) directly to the Canon:
> >
> > lpr -Pprint@canon test.ps
> >
> > This works, but we'd like to have the print jobs go thru the LPRng
> > print server, especially for processing of non-PS job files (to get
> > that automatic a2ps processing, etc.), and to get option selection
> > processing like duplex, staple, etc. I assume this requires somehow
> > setting up the printcap and ifhp.conf so that these jobs get forwarded
> > to the LPRng server, get processed, then get forwarded to the lpd on
> > the Canon.
> >
> > Any suggestions how to set this up? Would this process be simplified
> > if we went thru the overhead of upgrading to the latest LPRng/ifhp
> > versions? Anyone been thru this?
> >
> > We're running:
> >
> > LPRng-3.7.4
> > ifhp-3.4.4
> > Solaris-8
> >
> > Thanks.
> >
> > Dan
> >
> > PS: I know that this is probably in the docs. somewhere, but
> > generally it's taken me a long time to find what I need. Newer
> > versions of the docs. might be improved, but I'm worried about
> > backwards compatibility.
> >
> > PPS: I assume that page counts are out of the question? :-/
Thanks.
-Dan
--
Daniel E. Singer, System Administrator
Dept. of Computer Science, Duke University, Durham NC 27708 USA
"Non cognosco. In hoc tantum laboro."
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
