9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Laserjet Jetdirect problem
Date: Wed,  1 Sep 2010 14:11:29 -0400	[thread overview]
Message-ID: <AANLkTikFPKxc+nEwRTRCFoDNpFOrvF8pPQoeotvugL-D@mail.gmail.com> (raw)

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



             reply	other threads:[~2010-09-01 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 18:11 John Floren [this message]
2010-09-02 14:28 ` Russ Cox
2010-09-02 16:09   ` John Floren
2010-09-02 16:20     ` John Floren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikFPKxc+nEwRTRCFoDNpFOrvF8pPQoeotvugL-D@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).