Subject: RE: Need some help with printing on a LaserWriter IIg
From: Morgan Reed (morganr@home.com)
Date: Thu Jun 08 2000 - 01:34:06 EDT
Ok,
I checked my lpd.perms file and DEFAULT ACCEPT was and is the bottom line, I
ps ax | grep lpd and got what I think is the correct response:
1085 1 S 0.00 grep lpd
161 ? S 0.00 lpd MAIN
I made a /dev/null file.
still nothing.
Additionally though, I tried something; I put in lpr -P blahblah test1.ps
where blahblah is a nonexistant printer with no record created anywhere, and
I get the same response except it now reads transfer to blahblah@localhost
failed.
In my pointy little head, this suggests that the printcap is not getting the
correct information to the program. In essence, as far as lpr is concerned,
no printers at all exist. This is all getting me a little crazy, especially
since I can print using pap. If I couldn'tprint via pap I would have given
up and tried it with the serial plug. But because I can print with pap
tells me it is more than likely an lpr problem; but that still doesn't get
me any closer to printing.
Oh, I did check and fix the preceeding / in front of var. no change.
Anyone got any other grand ideas on getting lpr to work? I will sacrifice a
chicken to the linux gods if I thought it would work.
-----Original Message-----
From: Lancaster, David Matthew [mailto:c4ng2@unb.ca]
Sent: Wednesday, June 07, 2000 7:51 AM
To: Morgan Reed
Cc: netatalk-admins@umich.edu
Subject: RE: Need some help with printing on a LaserWriter IIg
This really does sound like more of a lpd/lpr problem. I think I sent you
a link to a discussion on a few known problems with Debian's lpd that
causes "transfer to lp@localhost failed" messages, did you find anything
applicable there? Version lprng_3.5.2-1.2 is problematic, check what
version you have.
Another possiblity is the /etc/lpd.perms file (debian slink/potato+)
The bottom line may read DEFAULT REJECT and you can change this to DEFAULT
ACCEPT (may have security implications, but fix that later).
Um, verify that lpd is running: ps ax | grep lpd
Have you tried dumping both 1) a plain ASCII file 2) a PS file to lp?
It's also possible its having problems communicating with the lpd spool
daemon. Check that your loopback interface is working (ping 127.0.0.1,
check ifconfig, try telneting to 127.0.0.1 & 127.0.0.1 printer).
Check your hosts.lpd entry, you might need your hostname in there.
Also check your hosts.deny for any entries that might affect this.
Suggest you may want to verity that lpd is working properly before
worrying about the netatalk portion. Any other printers to test with?
Also, try looking for some info from debian.com about this particular
problem.
(It just occured to me, I think you're running Debian, I seem to recall
that, but I'm not 100% sure...oh well...most of this might apply anyway.
;)
David Lancaster (506) 454-2167
690 Gregg Ct. Upper Apartment
Fredericton, NB Canada E3B 4H5
c4ng2@unb.ca "Don't anthropomorphize computers, they hate that."
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:59 EST