Subject: Re: problems with papd
From: Moritz Kaiser (ariser@fs.tum.de)
Date: Sun May 07 2000 - 13:00:29 EDT
On Sun, 7 May 2000, Dejan Muhamedagic wrote:
> Hi,
>
> On Sun, May 07, 2000 at 03:58:40PM +0200, Moritz Kaiser wrote:
> >
> > The first funny thing is, there is no termcap in my etc. I'm using
> > terminfo database.
>
> Not sure where this exactly stems from, but it definitely refers to
> printcap and not termcap. The point being, however, that the same
> syntax is used for both.
hmm, I also installed a common termcap but the results were the same.
>
> > The second funny thing is, if i remove /etc/netatalk/papd.conf and replace
> > it with touch /etc/netatalk/papd.conf, no errors are encountered.
>
> And you have no printers served :)
Oh, I _have_ printers served. But I cannot provide .PPDs which are
essential for driving Kyocera FS1700+.
>
> > My printcap has no errors, because I'm able to print via Samba without any
> > problems.
>
> This is interesting. It could be that there's a bug in papd function
> which is parsing /etc/printcap. Or, perhaps, lpd handles errors in
> printcap gracefully.
>
> > Ah, PS: my /etc/printcap:
> > 8<-----------------------
> > lp|kyo|kyocera:\
> > :lp=/dev/lp2:sd=/var/spool/lpd/kyo:\
> > :sh:pw#80:pl#72:px1440:mx#0:\
> Could there be an err^^or (px#1440)?
Even if when I disabled the first part of my printcap with hashes, the
same errors occured.
>
> Regardless, I would suggest that you try with a very simple printcap
I will do so.
> entry (referred to from papd.conf) and then try adding more capabilities
> until you find an error. Also, did you try changing the lp capability
> to pipe in papd.conf as it was suggested?
I did so. No effect.
desperately,
Moritz
__________________________________________________________
Moritz Kaiser
Studentische Vertretung, Technische Universitaet Muenchen
Europe / Germany
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:39 EST