Subject: Re: [netatalk-admins] Printing problem
From: Andras Kadinger (bandit@freeside.elte.hu)
Date: Mon Aug 17 1998 - 09:12:52 EDT
Hannu Krosing wrote:
>
> Andras Kadinger wrote:
> >
> >
> > Fixing papd is in the works;
>
> Do you have some more info about this: what exactly is wrong and who
> is working fixing it.
Currently is seems, that papd cannot properly handle binary postscript
streams; symptoms are excess CPU usage, corruption of the spooled data,
sometimes papd hangs; some people reported they can not spool jobs
beyond a certain size, which later was suggested to be the size of their
virtual memory.
Wesley Craig wrote:
> The latest theory (from A.DEURING@BIONIC.zerberus.de) is that this is a
> binary postscript problem. The 256M limit on your machine is your
> virtual memory. He has eliminated the problem with a heuristic that
> causes partial lines to be written, in the event of lines over some
> maximum with good results. I think a general solution would include
> implementing binary transmission in papd.
In the meantime, I am also crawling the source code of pap and papd and
will try to make them a bit more reliable and implement binary support,
and will look into creating support for lprng which was sought after on
the list before. (Anyone with pointers to lprng please email them to me,
if you can.)
Is anybody else working on these issues?
> I have currently problems with printing from Quark Xpress4.0, and it
> seems like the same problem
To test this, you might want to try to circumvent papd by writing the
PostScript data directly to a file and use that in the next step (lpr, I
guess). Also, there were a couple of printing problems in different
versions of QX4.0; check www.quark.com for updates.
Sincerely,
Andras Kadinger
bandit@freeside.elte.hu
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:33:08 EST