Ah ha!!!
Has this been brought to the attention to those individuals completing the
overhaul on Netatalk? A fix for this should be included in the next
release so we can all print from papd through LPD to any remote TCP/IP
LPR.
I would be interested in any patches to Netatalk papd that will allow it
to successfully work together with LPD for printing to remote LPRs over
TCP/IP.
After 2 years I finally got this problem answered by someone.
Please forward your patches. Thank you very much!
+--------------------------------------------------------------+
Russell E Glaue, Technologies Engineer [EMAIL PROTECTED]
Center for the Application of Information Technologies
101 Horrabin Hall, 1 University Circle, Macomb, Illinois 61455
http://www.cait.org http://cait.wiu.edu
On Tue, 10 Aug 1999, Ryan Cleary wrote:
> Russell E Glaue wrote:
> >
> > Do you atleast get something to print from the remote ethernet printer?
> > I assume you are using rm=ip.number.nnn.nnn in your /etc/printcap. I can't
> > get jobs to print from MAC to papd to LPR of the Ethernet printer over
> > TCP/IP. No one has been able to identify the problem for me so I might
> > assume there is a problem with the netatalk papd code in how it deals with
> > the BSD LPR in the Linux 2.2 Environment.
>
> I was having the same problem with RedHat 6.0 and preasun2.1.4-33, but I
> think I've figured out what's going on.
>
> I think it's really a problem with the BSD lpd code. lpd doesn't like
> to send queue files that are not 13 characters long to another lpd
> daemon. I've looked at the lpd source (specifically, function sendit()
> in lpd/printjob.c), and have a fix for the lpd code. I haven't tested
> it much, but it seems to work so far.
>
> Or, one could change papd so it only created spool files with 13
> character names.
>
> If you are interested in the details or an lpd patch, email me.
>
> --Ryan
>
