[LUNI] Long stange trip.

[Richard Reina]

Tony,

This is very useful advice and reassuring.  Thank you
very much..

Richard
--- Tony Schlemmer <aschlemm at comcast.net> wrote:

> On Wednesday 23 March 2005 19:59, Martin Maney
> wrote:
> > On Wed, Mar 23, 2005 at 02:41:11PM -0800, Richard
> Reina wrote:
> > > Although I have it partially working but cups
> won't
> > > let address the the remote printer as a remote
> > > printer.
> > >
> > > lpr -P lp at 192.168.0.4 document1
> > >
> > > does not work
> >
> > And that remote printer is what, an actual
> lpr-protocol device?  I'm
> > quite sure I've used the printer at host notation in
> the past - though not
> > very often - but perhaps never to spool to
> anything besides a remote
> > CUPS or a printer that operated using the ipp
> protocol.  The docs are,
> > as usual for CUPS despite their bulk, miserably
> vague about crucial
> > details, but I wonder if lpr only knows how to
> talk to ipp servers?
> >
> 
> "lpr" as supplied with the CUPS client knows how to
> work with a number of 
> different protocols including SMB, LPD, JetDirect,
> and IPP servers. I have a 
> number of different printers defined on my laptop
> using various protocols 
> including SMB, LPD, and JetDirect.
> 
> Rather than having the printer hardcoded into an
> application it should really 
> be read in from a configuration file or it could be
> defined as an environment 
> variable that the program inherits as part of its
> own environment. You would 
> then just need to setup the appropriate local
> printer entry through CUPS that 
> points to the the remote print server.
> 
> I haven't used Fedora Core and have only setup CUPS
> on Red Hat Enterprise 3 ES 
> and SuSE 9.x. Under Red Hat EL3 and SuSE they both
> use CUPs and interoperate 
> quite well in the office I work in.
> 
> As an example here's a list of my own laptop's
> printer settings. As you can 
> see CUPs supports quite a variety of different
> protocols for all of the 
> printers I have defined.
> 
> tschlemmer at tschlemm-dell:~> lpstat -t
> scheduler is running
> system default destination: hp8150n
> device for camljet: socket://192.168.10.201:9100/
> device for hp8150n: lpd://hp8150-ne:515/hp8150-n
> device for hp_laserjet4si:
> ipp://spong:631/printers/hp_laserjet4si
> device for ljet4: smb://HOMELAN/elmo.home.lan/ljet4
> device for lp: lpd://192.168.6.103:515/lp
> 
> [snip]
> 
> > > ... and that's how client print code is written.
> >
> > But surely it isn't a hardwired setting???
> >
> > --
> > If nature has made any one thing less susceptible
> than all others of
> > exclusive property, it is the action of the
> thinking power called an
> > idea, which an individual may exclusively possess
> as long as he keeps
> > it to himself; but the moment it is divulged, it
> forces itself into
> > the possession of every one, and the receiver
> cannot dispossess
> > himself of it.  -- Thomas Jefferson
> 
> Tony
> 
> -- 
> Anthony Schlemmer
> aschlemm at comcast.net
> -- 
> Linux Users Of Northern Illinois - Technical
> Discussion 
> http://luni.org/mailman/listinfo/luni
>