Hello Paul, lprng runs the inputfilters by default on the host on which the job is issued, and NOT on the server with the printer attached. That means the host has to do the work of rendering anything, the server lprng just forwards the job directly to the printer. Up to now I havn't found out how to change this (I'm sure there is a way), but I'd also like to keep resource hungry gs away from my laptop and let the printer server do the hard work so I'd be interested in a solution to the problem. Regards, Daniel
On Fri, 24 Nov 2000, Paul Schulz wrote: > Greetings, > > It seems that these two packages work really well together! but I have a > networking problem though.. and I would like to understand what is > going on. > > I have set lprng and magicfilter up on a server to print to a "HP > Laserjet 6p", a non-postscript printer. Works well when I print from > this host. (I've set the magicfilter to 'ljet2p'.) > > I set up my laptop to talk to print to [EMAIL PROTECTED], and it does, but > magicfilter doesn't process this postscript that it sends, and passes > it directly to the printer (which spits it out as stepped text, not > recognising the !%.) > > Why is this happening? Why isn't the postscript being processed by > magicfilter on the server? Standard stable (potato) Debian > installation on both.. > > lprng_3.6.12-8 > magicfilter_1.2.39 > > and the server queues set up with 'magicfilterconfig'. > > I don't want to have to install (not that it's overly difficult) > magicfilter on all the workstations. > > Any help appriciated. > Paul Schulz > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
