On 28 Jun 2000, Peter Gutowski wrote:
> I'm having problems trying to setup up printing on one of my Linux
> machines. The annoying thing about this is that I have an "identical"
> setup on my machine at home. For reasons perhaps only unix gurus can
> (hopefully!) explain, printing to the Linux machine using papd works
> at home, but not at work.
>
> Here's some info:
>
> Version Info:
>
> Redhat 6.1 on Packard-Hell 133mhz, netatalk-1.4b2+asun2.1.4 (b.37 I think)
>
>
> - - - - - - -/usr/local/atalk/etc/papd.conf - - - - - - -
>
> GhostScript to D800:\
> :pr=tiff:\
> :op=lp:\
> :pd=/usr/local/lib/ppd/ghostscript.ppd:
>
>
>
> - - - - - - - portion of /etc/printcap - - - - - - - - -
>
> tiff:\
> :sd=/var/spool/lpd/tiff:\
> :mx#0:\
> :sh:\
> :lp=/var/spool/lpd/tiff/null:\
> :if=/var/spool/lpd/tiff/tifffilt:
>
>
> I can print from my Mac to the Printer called "GhostScript to D800".
> No errors or problems. I can also print using lpr from the command
> line. The problem I seem to have is that something about the
> permissions on the file in the spool folder generated by papd seem to
> have the wrong owner or permissions. Here's what I mean:
>From what I can see in the papd code, it never tries to set the
owner/group of the file with the op setting. It uses op to set some
options in the lpr control file, like so:
lp.c: fprintf( cfile, "P%s\n", printer->p_operator );
lp.c: fprintf( cfile, "L%s\n", printer->p_operator );
printer->p_operator holds the value of op from the config file.
I would highly recommend that you pipe the output to lpr instead of
letting papd meddle in the spool directory itself. You'll avoid all these
permissions problems. In your papd.conf file, change ":pr=tiff:\" to
":pr=|/usr/bin/lpr -Ptiff:\".
Andy
