* [9fans] Laserjet Jetdirect problem @ 2010-09-01 18:11 John Floren 2010-09-02 14:28 ` Russ Cox 0 siblings, 1 reply; 4+ messages in thread From: John Floren @ 2010-09-01 18:11 UTC (permalink / raw) To: Fans of the OS Plan 9 from Bell Labs I decided to try and configure my system to print to the lab's network printer, an HP Laserjet 4014 with JetDirect enabled. I can happily print to it from Linux using CUPS. For reference, my Plan 9 server is called p9 and the printer is called prec7. Based on the example I saw in the config file, I did this: prec7 - p9 tcp!prec7!9100 81920 post+600dpi generic generic generic generic tcppost But, when I try a simple query: cpu% lp -D -dprec7 -q grep '^prec7[ ]' /sys/lib/lp/devices bind -b /sys/lib/lp/stat /bin exec generic lpsend.rc p9 echo -dprec7 -q sleep 5 test -e /net/tcp/clone ndb/query sys p9 dom lpsend tcp!p9!printer Sep 1 14:09:26 failed to receive ACK, read failed Sep 1 14:09:26 failed to receive ACK before sending data exit 'lpsend: no dialstring' exit '|lpsend.rc 28728: lpsend: no dialstring' If I go in and move /rc/bin/service/!tcp515 to tcp515 and try again, 'ps' shows that lots of lpdaemon, generic, lpsend.rc, and lpsend processes get started, and the memory usage slowly climbs and climbs, but nothing ever happens. Anybody else experienced this? John -- "With MPI, familiarity breeds contempt. Contempt and nausea. Contempt, nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] Laserjet Jetdirect problem 2010-09-01 18:11 [9fans] Laserjet Jetdirect problem John Floren @ 2010-09-02 14:28 ` Russ Cox 2010-09-02 16:09 ` John Floren 0 siblings, 1 reply; 4+ messages in thread From: Russ Cox @ 2010-09-02 14:28 UTC (permalink / raw) To: Fans of the OS Plan 9 from Bell Labs > 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] Laserjet Jetdirect problem 2010-09-02 14:28 ` Russ Cox @ 2010-09-02 16:09 ` John Floren 2010-09-02 16:20 ` John Floren 0 siblings, 1 reply; 4+ messages in thread From: John Floren @ 2010-09-02 16:09 UTC (permalink / raw) To: Fans of the OS Plan 9 from Bell Labs On Thu, Sep 2, 2010 at 10:28 AM, Russ Cox <rsc@swtch.com> 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] Laserjet Jetdirect problem 2010-09-02 16:09 ` John Floren @ 2010-09-02 16:20 ` John Floren 0 siblings, 0 replies; 4+ messages in thread From: John Floren @ 2010-09-02 16:20 UTC (permalink / raw) To: Fans of the OS Plan 9 from Bell Labs Well, it looks like the solution was to do this: prec7 - p9.<mydomain> tcp!prec7.<mydomain>!9100 81920 post+600dpi+nohead generic generic generic generic tcppost FIFO With tcp515 disabled. I guess the full domain names are important, rather than /lib/ndb names? Anyway, now I can print. John On Thu, Sep 2, 2010 at 12:09 PM, John Floren <slawmaster@gmail.com> wrote: > On Thu, Sep 2, 2010 at 10:28 AM, Russ Cox <rsc@swtch.com> 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 > -- "With MPI, familiarity breeds contempt. Contempt and nausea. Contempt, nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-09-02 16:20 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-09-01 18:11 [9fans] Laserjet Jetdirect problem John Floren 2010-09-02 14:28 ` Russ Cox 2010-09-02 16:09 ` John Floren 2010-09-02 16:20 ` John Floren
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).