Yes I know, I've set up for testing purpose some forwarding queues. The
simplest way (before I took out the "default_remote_host"-line in
lpd.conf):
lexmark1:\
:client:[EMAIL PROTECTED]:force_localhost@
brought:
- lpc status all on the client showed 0 printers
- print command went well, job arrived at the server, no filter was
processed
THEN I set up following (clientside)
lexmark1:\
:client:[EMAIL PROTECTED]:force_localhost@:\
:control_filter= -$ /usr/lib/filters/classA.sh $Z
brought:
- lpc status all still showed nothing
- print command ok, job at server, filtering went ok (and why? Because I
filtered on the CLIENT)
By now I ask myself, why I should setup one or two printserver when I
still have to maintain client's printcap (whether I have to type 2 or 10
lines per printer) ...
Am Mit, 2003-09-17 um 13.13 schrieb George Bell:
> On Wednesday 17 September 2003 04:50, Gruber Stefan wrote:
> > Hello list!
> >
> > Have a little problem with my client/server environment.
> >
> > Server: SuSE, with large printcap, ifhp-Filter and control_filter, LPRng
> > 3.8.12 (hostname: bacs3)
> > Client: HPUX 11.0, no printcap, LPRng 3.8.22 (hostname: test1)
> >
> > In the client's lpd.conf I have the entry "default_remote_host=bacs3";
> > client's lpd-daemon is running, lpc status all shows all bacs3-printer,
> > print commands are processed and will be printed, unfortunately without
> > options (like landscape, pitch, duplex etc)
> > Until now it looks fine BUT: ifhp and control filter were ignored
> > I would say, this means that my job, triggered on the client is SPOOLED
> > on the client (what I don't want) and not at the server.
> >
> > Perhaps I have misunderstood the concept: what I want is a client where
> > I don't have to maintain a printcap! In other words: passes the whole
> > work of spooling, filtering and printing to the server.
> >
>
>
> I think you can print directly to a network printer with the lpr command:
> lpr -P printer where "printer" specifies the host with the print server in
> some way. However, I think this sort of thing is usually done by setting
> up a simple forwarding que on the "client". I use Suse 8.0 to set up an HP
> printer on one host as well as to print from another host. Yast sets up the
> printer on the computer where the printer is connected as well as set up a
> forwarding que on the remote host. Then, the forwarding que on the remote
> host("client") just forwards the job to the que on the server with the
> printer where all the filters and printing drivers are applied.
>
> George
>
#####################################################################################
This e-mail message has been scanned for Viruses and Content
by MailMarshal
For more information please visit www.marshalsoftware.com
#####################################################################################
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
