| Christian Ullrich on Tue, 15 Jan 2002 16:31:00 +0100 (CET)(envelope-from owner-apsfilter-help@apsfilter.org) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: apsfilter doesn't work on server |
* Michael Loßin wrote on Tuesday, 2002-01-15: > On 15-Jan-02 Christian Ullrich wrote: > Which spooler do you use on those? BSD lpd on the Server, LPRng on the client. > Please try to use LPRng on server *and* client machines, since > the old BSD-style lpd has some problems with remote printing. I'll try that ASAP. > > - When I try to print anything else, say, a tar file, the job just > > goes somewhere and I never hear of it again. > > That "somewhere" is your printer, but it doesn't speak tar, > so that file is just discarded. That sounds reasonable, although I don't quite buy into it yet. The printer insists on a ^D at the end of a job, otherwise it keeps blinking (until some timeout or other elapses). In this case, it didn't even start. > > Is it at all possible to just send the data from the client to the > > server, and let the server do all the file type recognition and > > PostScript conversion? Or do I have to do that on every client > > separately? > > That would pretty much defeat the purpose of a printer server, > so it should be possible, of course. You give me hope. > ># bounce queue? > > lp:\ > > :lp=/dev/null:\ > > :sd=/var/spool/lpd/lp: > > > > /etc/apsfilter/lp/lpr.conf contains "REMOTE_NAME=real_lp". > > As long as there's no if=... line for "lp" that calls apsfilter, > it's not useful to create /etc/apsfilter/lp/lpr.conf ... it > simply won't be used :) You are right, of course. I will try that as well. > However, you wouldn't need the bounce queue at all if the > filter would be called properly... Catch 22, I guess :^) > > I'm sufficiently confused now... Hasn't anyone succeeded in > building a printer server with apsfilter yet? > Or is it just the BSD-lpd that causes this? Well, I have searched the Internet quite a bit for people with either the same problem, or, even better, a solution. I haven't found anything. > > relevant part of printcap on client: > > > > lp_net|remote printer on ser1:\ > > :sd=/var/spool/lpd/lp_net:\ > > :rm=ser1:\ > > :rp=lp:\ > > :bk:sh:mx#0: > > Do we need an :lp=...: line here? Even if it's just > :lp=/dev/null: or :lp=: ? IIRC, if I include an lp= line, LPRng spits at me for doing both lp and rm. -- Christian Ullrich Registrierter Linux-User #125183 "Deliver."