Subject: Re: printing problem
From: Carsten Neumann (deltor@snafu.de)
Date: Fri Jan 26 2001 - 17:18:11 EST
On Fri, 26 Jan 2001, Richard Goldberg wrote:
> Hi all,
>
> My papd.conf file is set up as follows:
> Colour Test:\
> :pr=test:\
> :op=lp:\
> :pd=/etc/atalk/ppd/lexmark_optrac710.ppd:
>
> When I try to print someting, I get an error on the mac saying
> "Document could not be printed on printer "Printername" because of a
> PostScript error". In the log file on my atalkd server I get:
>
> Jan 26 13:31:27 <server> papd[9128]: getppdent: line too long
> Jan 26 13:31:27 <server> papd[9128]: lp_init: lock: No such file or directory
> Jan 26 13:31:27 <server> papd[9128]: lp_open failed
>
> I thought the "line too long "error was due to the lf/cr issue between mac
> and unix but I ran tr "\015" "\012" < orig.ppd > temp.ppd and the
> error still comes up.
Have you tried to setup the printer on your Mac after tr-ing your PPD file?
(and renaming the temp file? ;-))
Just to re-read the ppd file.
>
> I know I can fix the other error (lp_init/lp_open) by changing the conf
> file to
> :pr=|/usr/bin/lpr -Ptest:\
> are there any disadvantages to this?
I had similar problems: job was queued but no daemon started.
The error messages were others:
Jan 11 03:23:19 athlet papd[5733]: lp_conn_unix connect /dev/printer: Connection refused
Jan 11 03:23:19 athlet papd[5733]: lp_print: lp_conn_unix: Connection refused
Just piping to lpr solved this.
Had no problems until now.
>
> Are there any other ways to fix this problem?
>
> Why does this problem happen?
Are the spool directory and its files owned by lp?
What is your printcap entry for test?
>
> Thanks
Regards
Carsten
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:31 EDT