Subject: Re: [netatalk-admins] papd problem - binary postscript
From: Les Klein (les@psgroup.cix.co.uk)
Date: Tue May 26 1998 - 04:11:56 EDT
> I saw someone has posted question about this, but no one replied.
> The problem is:
> When printing Postscipt file from Mac, something weird happens - papd
> consumes 90% of CPU while processing something unknown. Only beginning of
> the file is transmitted to the spool directory of lpr and nothing happens.
> I was waiting about 20 minutes and had to cancel print job from the Mac. I
> think something is wrong with the papd.
> The file was a binary postscipt - for ascii postscript everything seems to
> be ok.
> The transmitted fragment of postscript ends just before the beginning of
> binary data.
> The same thing happens when I try to print this file not from Mac, but
> using pap client.
>
I have the same problem. Also, papd never closes PAP properly if the very
last character in a PostScript file is Ctrl-D ('\004'). Looking at the
source code for 1.4b2 it looks like netatalk/papd can not work with binary
files. It does however look quite easy to correct. Can anyone confirm/deny
this or say if they have already modified the code before I have a go?
Thanks
Les Klein.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:45 EST