On Wed, 20 Apr 2005 11:10:11 -0500, Richard Rauch <rkr@olib.org> wrote:
> On Wed, Apr 20, 2005 at 10:21:41AM -0400, James K. Lowden wrote:
> > On Wed, 20 Apr 2005 06:38:31 -0500, Richard Rauch <rkr@olib.org>
> > wrote:
> > > I am getting a rather opaque error message from lpd.  Maybe someone
> > > can help.
> > > 
> > > Apr 20 06:07:12 cyclopes lpd[6021]: ps: job could not be printed
> > > (cfA003psocrates)
> > ...
> > >   <printing system> -=> <cyclopes> -=> <prometheus>
> > ...
> > > This all used to work with a NetBSD 1.6 box (hermes) standing in
> > > for cyclopes. Cyclopes is running 2.0.
>  [...]
> > 
> > Could it be /etc/hosts.lpd on prometheus?  
> 
> In fact, at one point it was.  But that was fixed.  I still have
> this problem.

Well, I don't know, but I just had a similar problem, and I unjammed it in
a most unlikely way.  

I kept trying to print from A to B, where my (highly recommended) Lexmark
E322 is attached to B's lpa0.  I went through the usual motions and was
about to begin hunting for some small animal....

I guess I had queued a few one-page jobs, but no sign of life (let alone
urgency) on the part of the printer, nor any messages in
/var/log/lpd-errs.  Out desperation, I tried "telnet B 515".  That
elicited a reproach from (I guess) the lpd daemon: it disconnected the
session stating that it had come from an invalid port.  BUT: then my jobs
printed!  

You tell me.   

--jkl