Date: Wed, 16 Jan 2002 12:11:31 +0100 From: Christian Ullrich <chris@chrullrich.de> To: apsfilter-help@apsfilter.org Cc: Garance A Drosihn <drosih@rpi.edu>, desmo@bandwidth.org, freebsd-stable@freebsd.org Subject: Re: 4.4R: if: doesn't get started when getting remote print job (Re: apsfilter doesn't work on server) Message-ID: <20020116111131.GA19728@christian.chrullrich.de> In-Reply-To: <20020116091030.GA16535@titan.klemm.gtn.com> References: <20020115062456.GA13349@christian.chrullrich.de> <XFMail.020115124543.phallobst@web.de> <20020115151846.GA14953@christian.chrullrich.de> <20020115213522.GA15920@christian.chrullrich.de> <20020116091030.GA16535@titan.klemm.gtn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Andreas Klemm wrote on Wednesday, 2002-01-16: > On Tue, Jan 15, 2002 at 10:35:22PM +0100, Christian Ullrich wrote: > > Warning: The following is _very_ detailed. It took me three hours > > to do it all and write it down. If there is _any_ information > > missing, please do not hesitate to ask. [...] > > 6. I built apsfilter-7.2.1, with the following options enabled: > > - A4 - A4 papersize > > - GS_NO_X11 - Postscript for non-PS printer, no X11 > > - GS_PDF_CRYPT - print encrypted PDF files using gs > > - PSUTILS - for pseudo duplex printing + paper handling > > - A2PS - ASCII files in different styles/orientation > > - DVIPS - TeX DVI files > > - HTML2PS - HTML documents > > - TROFF - Troff documents > > - BZIP2 - print bunzip2 compressed documents > > On the first attempt to "make install" apsfilter, I was told that > > the file /usr/local/etc/apsfilter existed. It was a symbolic link > > to /etc/apsfilter, which I had renamed in step 2. I removed the > > link and installed again. This time it worked fine. > > If you had updated the ports collection you would have used > apsfilter 7.2.1, which includes a fix for that by using > ln -sf ... I did update the ports collection, via cvsup. And I built and installed apsfilter 7.2.1. I just noticed that I forgot to "pkg_delete" version 7.1.1 before installing the new version, but as /usr/local/share/apsfilter/bin/apsfilter is: # $ApsCVS: src/apsfilter/bin/apsfilter.in,v 1.212.2.7 2002/01/09 21:06:30 andrea s Exp $ ############################################################################## # # apsfilter 7.2.1 # --------- I don't think that I'm still running the old version. > > 10. I installed that configuration under the name "ascii" and finished > > the SETUP script for the time being. > > > > This is the generated printcap (comments stripped): > > > > ascii|PS;r=600x600;q=medium;c=gray;p=a4;m=ascii:\ > > :lp=/dev/lpt0:\ > > :if=/etc/apsfilter/basedir/bin/apsfilter:\ > > :sd=/var/spool/lpd/ascii:\ > > :lf=/var/spool/lpd/ascii/log:\ > > :af=/var/spool/lpd/ascii/acct:\ > > :mx#0:\ > > :sh: > > Why you named it ASCII ? I wanted to save "lp" for a future configuration with automatic file type recognition, so that there would no random bits of old configurations lying around. > > 11. I started LPRng and found this line in syslog: > > > > Jan 15 20:41:02 ser1 checkpc[73259]: ascii: Checkwrite: fcntl F_SETFL > > of '/dev/lpt0' failed - Operation not supported by device > > > > Similar output was generated by calling "checkpc -f". But sending > > data to the printer was never the problem, so I'm currently not > > much concerned about it. > > Ask FreeBSD port maintainer, LPRng people. Of course. There is a lot of possibly unnecessary information in my mail, but I gave as much detail as possible. > > 19. Now for the client. Using SuSE's YaST configuration tool, > > I configured a simple network printer: > > > > ascii|remote printer on ser1:\ > > :sd=/var/spool/lpd/ascii:\ > > :rm=ser1:\ > > :rp=ascii:\ > > :bk:sh:mx#0: > > > > 20. "lpq -Pascii" on the client showed that the printer status was > > accessible. > > > > 21. "lpr -Pascii /etc/printcap" from the client produced the usual > > staircased text. Even an "ASCII only" apsfilter configuration > > on the server didn't work, and still doesn't. Because the printer > > stopped blinking, I'm sure that it got the text file directly, > > without apsfilter in between. > > > > I'm out of ideas. What about you out there? > > As workaround install apsfilter on the client, to compute print > data on the client, so that the correct data stream enters the > server. Well, that's just what I wanted to avoid in the first place. If I had considered that the optimal solution, I would not have started messing with it. I will do it that way again for the time being, though. > is a bug in 4.4-RELEASE. Well now you installed LPRng on FreeBSD > which normally is not necessary, since FreeBSD's lpd is not so > "stock" and limited as all the other un-fixed versions around. Well, when it didn't work with BSD lpd, I grasped for any straw. > Concerning lpd I'd remove the LPRng port if Garant has replied > to you and I'm sure, that he will be helpful to you. But then > you should re-install lpd from /usr/src, that shouldn't be a problem > with FreeBSD ... No, that shouldn't be too hard. > Additionally you could then try to update to 4.5-RC, since then you > can both work on the latest and greatest -STABLE version of FreeBSD, > so that there every bug is shaken out ... > > And I remember people have merged something from -current into the > printing subsystem, maybe this already helped. > > And please use apsfilter 7.2.1. I did. I really did. Thanks for your answer no. 1. -- Christian Ullrich Registrierter Linux-User #125183 "Deliver." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020116111131.GA19728>