On Thu, Sep 2, 2010 at 10:28 AM, Russ Cox <[email protected]> wrote: >> prec7 - p9 tcp!prec7!9100 81920 post+600dpi generic >> generic generic generic tcppost > > Your spooler is generic but I think you want lpdsend. > Look at the entry for "vogon" in the standard /sys/lib/lp/devices. > > Russ > >
Having cloned the entry for vogon: prec7 - p9 prec7 - post+600dpi generic lpdspool lpd - - If I try to print, eventually lp just returns. Nothing prints, no error messages, nothing. Aha, I say, maybe I'll try moving /rc/bin/service/!tcp515 to tcp515 and try again. At that point, my cpu and network get very busy, I can see lpd and lpdaemon and lpspool, etc. all running, but yet again nothing ever prints. If I change the entry to start like this: prec7 - p9 tcp!prec7!9100 since I'm not sure how it's supposed to know to connect to port 9100 by itself, lp -dprec7 -q gives: connecting to tcp!p9!printer trying from port 721...connected device prec7.ce.rit.edu is not in /sys/lib/lp/devices If I try to print, again, no error is given, but /sys/lib/lp/log/lpdaemonl gets: Sep 2 12:04:44 [17619] -dprec7.<mydomain> -Mp9.<mydomain> -ujohn Sep 2 12:04:44 [17619] read error; lost connection I might be confused here, but it seems to me like the entry for vogon is saying "There's an lp daemon on alice, connect to that and tell it to print on its printer called vogon". That doesn't really make sense for me, because I'm already printing *from* p9. p9 has a printer named prec7, sure, but that just points right back at p9 again... it seems like a recipe for an infinite loop at the least. Somewhere, at some point, don't I need to say "Send some data to tcp!prec7!9100"? Printers have never been my strong point; I'm usually just good enough to get it set up in CUPS :) John -- "With MPI, familiarity breeds contempt. Contempt and nausea. Contempt, nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich
