Ok, sounds like you've narrowed it down a bit. 

Check if lpd is able to read your printcap file correctly.
Do a "lpc status", you should get something similar to:
lp:
        queuing is enabled
        printing is enabled
        no entries
        no daemon present

If not, lpd is unable to parse your printcap. I found printcap can be
picky...I had a problem which was either an extra space, tab, or CR
character at the end a printer def, and it wouldn't work till I deleted
it. If you want, I can email you a copy of my printcap, and you can check
if that's your problem.

Another thing I just noticed...in your ps ax | grep lpd, it shows the lpd
process with an argument "MAIN".  According to my RH6 man pages, lpd only
takes one argument, which is the port#...
What happens when you type:
a) telnet localhost printer
b) telnet localhost MAIN

And just to clarify, DID you try to update lprng???

David Lancaster                       (506) 454-2167
  690 Gregg Ct.                       Upper Apartment
  Fredericton, NB  Canada             E3B 4H5
  [EMAIL PROTECTED]       "Don't anthropomorphize computers, they hate that."

On Thu, 8 Jun 2000, Morgan Reed wrote:

> 
> 
> 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.

Reply via email to