9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Newbie question on printing
Date: Tue, 26 Jul 2005 12:33:13 +0100	[thread overview]
Message-ID: <954853031a0cf97c301740a691d34b4e@tombob.com> (raw)
In-Reply-To: <ee9e417a050726040555800254@mail.gmail.com>

> On 7/26/05, Steve Simon <steve@quintile.net> wrote:
>> I print to lasers which are connected via HP jet-direct boxes using:
>> 
>> /sys/lib/lp/devices:
>> slp_a3 SLP_A3 slp-oh-a3 A4_LPQ  -  post+duplex+nohead  generic  lpdspool  lpd  -  - FIFO
> 
> An even better solution.  Try this first.  The difference between
> this and your original devices line is that this one uses the
> printer's name as the "spooler machine", i.e. the address to
> send the job to.
> 
> Russ

Steve, Russ, thank you very much. I now have
clp550n_ps	robbys-room	clp550n	A4_LPQ	-	post+600dpi+nohead	generic	lpdspool	lpd	-	-	FIFO

and from 'lp -D -dclp550n_ps -q' I get

grep '^clp550n_ps[ 	]' /sys/lib/lp/devices
bind -b /sys/lib/lp/stat /bin
exec lpd
echo transmission log:
transmission log:
test -r /sys/lib/lp/log/clp550n_ps.st
echo printer queue:
printer queue:
/386/bin/aux/lpdsend -q -dA4_LPQ clp550n
connecting to tcp!clp550n!printer
 trying from port 721...connected
PortThru lpd: No Jobs on this queue
exit ''

Lovely.

I have two simple questions, so I can understand what is happening.
The A4_LPQ, what does that do?  It is in the OUT_DEV field but ain't a
device, and just guessing I would assume it names the queue to use.
Is that corerct?  Could that be any text, or does the LPD in the
printer have ideas on how to name and handle queues?

Second, is it good practice to have the machine name of the printer
(/lib/ndb/local entry) be different from the /sys/lib/lp/devices
printer name?  I know that I can add more "virtual" printers to turn
on duplex and color and what not.

I can't actually verify that a page got printed, as I'm doing this
remotely via a drawterm.  But maybe I'll have a page sitting there for
me when I get home tonight.

Thanks again,
Robby



  reply	other threads:[~2005-07-26 11:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 10:29 Robert Raschke
2005-07-26 10:57 ` Steve Simon
2005-07-26 11:05   ` Russ Cox
2005-07-26 11:33     ` Robert Raschke [this message]
2005-07-26 12:06       ` Russ Cox
2005-07-26 15:46         ` Jack Johnson
2005-07-26 15:59           ` Russ Cox
2005-07-26 16:07           ` Ronald G. Minnich
2005-07-26 16:35             ` Jim McKie
2005-07-26 16:55               ` Jack Johnson
2005-07-26 17:28                 ` Ronald G. Minnich
2005-07-26 18:49               ` andrey mirtchovski
2005-07-26 16:44             ` Jack Johnson
2005-07-26 11:03 ` Russ Cox

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=954853031a0cf97c301740a691d34b4e@tombob.com \
    --to=rrplan9@tombob.com \
    --cc=9fans@cse.psu.edu \
    /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).