<HTML
><HEAD
><TITLE
>Networks</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.49"><LINK
REL="HOME"
TITLE="The Printing HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Ghostscript."
HREF="ghostscript.html"><LINK
REL="NEXT"
TITLE="Windows-only printers"
HREF="winprinters.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Printing HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="ghostscript.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="winprinters.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="NETWORK"
>11. Networks</A
></H1
><A
NAME="AEN2324"
></A
><P
> One of the features of most spoolers is that they support printing
over the network to printers physically connected to a different
machine, or to the network directly. With the careful combination
of filter scripts and assorted utilities, you can print
transparently to printers on all sorts of networks.
</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORK-TO-UNIX"
>11.1. Printing to a Unix/lpd host</A
></H2
><A
NAME="AEN2329"
></A
><A
NAME="AEN2332"
></A
><A
NAME="AEN2335"
></A
><P
> To allow remote machines to print to your printer using the LPD
protocol, you must list the machines in
<I
CLASS="EMPHASIS"
>/etc/hosts.equiv</I
> or
<I
CLASS="EMPHASIS"
>/etc/hosts.lpd</I
>. (Note that
<I
CLASS="EMPHASIS"
>hosts.equiv</I
> has a host of other effects; be
sure you know what you are doing if you list any machine there).
You can allow only certain users on the other machines to print to
your printer by usign the <I
CLASS="EMPHASIS"
>rs</I
> attribute; read
the <TT
CLASS="LITERAL"
><A
HREF="http://www.linuxprinting.org/man/lpd.8.html"
TARGET="_top"
>lpd</A
></TT
> man page for information on this.
</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-UNIX-WITH-PDQ"
>11.1.1. With <TT
CLASS="LITERAL"
>pdq</TT
></A
></H3
><A
NAME="AEN2347"
></A
><A
NAME="AEN2350"
></A
><P
> With PDQ, you define a printer with the interface type "bsd-lpd".
This interface takes arguments for the remote hostname and queue
name; the printer definition wizard will prompt you for these.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-UNIX-WITH-LPD"
>11.1.2. With <TT
CLASS="LITERAL"
>lpd</TT
></A
></H3
><P
> To print to another machine, you make an
<I
CLASS="EMPHASIS"
>/etc/printcap</I
> entry like this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
># REMOTE djet500
lp|dj|deskjet:\
:sd=/var/spool/lpd/dj:\
:rm=machine.out.there.com:\
:rp=printername:\
:sh:</PRE
></TD
></TR
></TABLE
>
Note that there is still a spool directory on the local machine
managed by <TT
CLASS="LITERAL"
>lpd</TT
>. If the remote
machine is busy or offline, print jobs from the local machine
wait in the spool area until they can be sent.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-UNIX-WITH-RLPR"
>11.1.3. With <TT
CLASS="LITERAL"
>rlpr</TT
></A
></H3
><A
NAME="AEN2364"
></A
><A
NAME="AEN2366"
></A
><P
> You can also use <I
CLASS="EMPHASIS"
>rlpr</I
> to send a print job
directly to a queue on a remote machine without going through the
hassle of configuring lpd to handle it. This is mostly useful in
situations where you print to a variety of printers only
occasionally. From the announcement for
<I
CLASS="EMPHASIS"
>rlpr</I
>:
</P
><P
> Rlpr uses TCP/IP to send print jobs to lpd servers anywhere on a
network.
</P
><P
> Unlike lpr, it *does not* require that the remote printers be
explicitly known to the machine you wish to print from,
(e.g. through <I
CLASS="EMPHASIS"
>/etc/printcap</I
>) and thus is
considerably more flexible and requires less administration.
</P
><P
> rlpr can be used anywhere a traditional lpr might be used, and is
backwards compatible with traditional BSD lpr.
</P
><P
> The main power gained by rlpr is the power to print remotely
*from anywhere to anywhere* without regard for how the system you
wish to print from was configured. Rlpr can work as a filter
just like traditional lpr so that clients executing on a remote
machine like netscape, xemacs, etc, etc can print to your local
machine with little effort.
</P
><P
> Rlpr is available from <TT
CLASS="LITERAL"
><A
HREF="ftp://metalab.unc.edu/pub/Linux/system/printing/"
TARGET="_top"
>Metalab</A
></TT
>.
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORK-TO-WINDOWS"
>11.2. Printing to a Windows or Samba printer</A
></H2
><A
NAME="AEN2383"
></A
><A
NAME="AEN2386"
></A
><P
> There is a Printing to Windows mini-HOWTO out there which has more
info than there is here.
</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-WINDOWS-WITH-PDQ"
>11.2.1. From PDQ</A
></H3
><A
NAME="AEN2392"
></A
><P
> There is not a prebuilt smb interface that I am aware of, but it
would be fairly easy to create using the model set by the
Netatalk-based appletalk interface. Someone please create one
and submit it for inclusion!
</P
><P
> Read the Windows/LPD section below for more tips on how to do it.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-WINDOWS-WITH-LPD"
>11.2.2. From LPD</A
></H3
><A
NAME="AEN2399"
></A
><P
> It is possible to direct a print queue through the <TT
CLASS="LITERAL"
><A
HREF="http://www.linuxprinting.org/man/smbclient.1.html"
TARGET="_top"
>smbclient</A
></TT
> program (part of the samba suite)
to a TCP/IP based SMB print service. Samba includes a script to
do this called <TT
CLASS="LITERAL"
>smbprint</TT
>. In short,
you put a configuration file for the specific printer in question
in the spool directory, and install the <TT
CLASS="LITERAL"
>smbprint</TT
> script as the
<I
CLASS="EMPHASIS"
>if</I
>.
</P
><P
> The <I
CLASS="EMPHASIS"
>/etc/printcap</I
> entry goes like this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>lp|remote-smbprinter:\
:sh:\
:lp=/dev/null:\
:sd=/var/spool/lpd/lp:\
:if=/usr/local/sbin/smbprint:</PRE
></TD
></TR
></TABLE
>
</P
><P
> You should read the documentation inside the <TT
CLASS="LITERAL"
>smbprint</TT
> script for more information on how
to set this up.
</P
><P
> You can also use <TT
CLASS="LITERAL"
>smbclient</TT
> to
submit a file directly to an SMB printing service without
involving <TT
CLASS="LITERAL"
>lpd</TT
>. See the man page.
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORK-TO-NETWARE"
>11.3. Printing to a NetWare Printer</A
></H2
><A
NAME="AEN2419"
></A
><A
NAME="AEN2422"
></A
><A
NAME="AEN2425"
></A
><P
> The ncpfs suite includes a utility called <TT
CLASS="LITERAL"
>nprint</TT
> which provides the same functionality
as <TT
CLASS="LITERAL"
>smbprint</TT
> but for NetWare. You
can get ncpfs from <A
HREF="ftp://metalab.unc.edu/pub/Linux/system/filesystems/ncpfs/"
TARGET="_top"
>Metalab</A
>. From the LSM entry for version 0.16:
</P
><P
> <SPAN
CLASS="QUOTE"
>" With ncpfs you can mount volumes of your netware server under
Linux. You can also print to netware print queues and spool
netware print queues to the Un*x print spooler. You need
kernel 1.2.x or 1.3.54 and above. ncpfs does NOT work with any
1.3.x kernel below 1.3.54.
"</SPAN
>
</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-NETWARE-WITH-LPD"
>11.3.1. From LPD</A
></H3
><A
NAME="AEN2435"
></A
><P
> To make <TT
CLASS="LITERAL"
>nprint</TT
> work via lpd, you
write a little shell script to print stdin on the NetWare
printer, and install that as the <I
CLASS="EMPHASIS"
>if</I
> for an
lpd print queue. You'll get something like:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>sub2|remote-NWprinter:\
:sh:\
:lp=/dev/null:\
:sd=/var/spool/lpd/sub2:\
:if=/var/spool/lpd/nprint-script:</PRE
></TD
></TR
></TABLE
>
The <TT
CLASS="LITERAL"
>nprint-script</TT
> might look
approximately like:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>#! /bin/sh
# You should try the guest account with no password first!
/usr/local/bin/nprint -S net -U name -P passwd -q printq-name -</PRE
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORK-TO-APPLE"
>11.4. Printing to an EtherTalk (Apple) printer</A
></H2
><A
NAME="AEN2446"
></A
><A
NAME="AEN2449"
></A
><P
> The netatalk package includes something like <TT
CLASS="LITERAL"
>nprint</TT
> and <TT
CLASS="LITERAL"
>smbclient</TT
>. Others have documented the
procedure for printing to and from an Apple network far better
than I ever will; see the <A
HREF="http://thehamptons.com/anders/netatalk/"
TARGET="_top"
>Linux
Netatalk-HOWTO</A
>.
</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORK-TO-APPLE-FROM-PDQ"
>11.4.1. From PDQ</A
></H3
><A
NAME="AEN2459"
></A
><P
> PDQ includes an interface declaration called "appletalk". This
uses the Netatalk package to print to a networked Apple printer.
Just select this interface in xpdq's "Add printer" wizard.
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORKED-PRINTERS"
>11.5. Printing to a networked printer</A
></H2
><A
NAME="AEN2464"
></A
><A
NAME="AEN2467"
></A
><A
NAME="AEN2471"
></A
><A
NAME="AEN2474"
></A
><P
> Many printers come with an ethernet interface which you can print
to directly, typically using the LPD protocol. You should
follow the instructions that came with your printer or its network
adaptor, but in general, such printers are "running" lpd, and
provide one or more queues which you can print to. An HP, for
example, might work with a printcap like:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>lj-5|remote-hplj:\
:sh:\
:sd=/var/spool/lpd/lj-5:\
:rm=printer.name.com:\
:rp=raw:</PRE
></TD
></TR
></TABLE
>
or, using the PDQ bsd-lpd interface arguments of
REMOTE_HOST=printer.name.com and QUEUE=raw.
</P
><P
> HP Laserjet printers with JetDirect interfaces generally support
two built in lpd queues - "raw" which accepts PCL (and possibly
Postscript) and "text" which accepts straight ascii (and copes
automatically with the staircase effect). If you've got a
JetDirect Plus3 three-port box, the queues are named "raw1",
"text2", and so forth.
</P
><P
> Note that the ISS company has identified an assortment of denial
of service attacks which hang HP Jetdirect interfaces. Most of
these have been addressed beginning in Fall 98. These sorts of
problems are common in embedded code; few appliance-style devices
should be exposed to general Internet traffic.
</P
><A
NAME="AEN2481"
></A
><P
> In a large scale environment, especially a large environment where
some printers do not support PostScript, it may be useful to
establish a dedicated print server to which all machines print and
on which all ghostscript jobs are run. This will allow the queue
to be paused or reordered using the topq and lprm commands.
</P
><P
> This also allows your GNU/Linux box to act as a spool server for the
printer so that your network users can complete their print jobs
quickly and get on with things without waiting for the printer to
print any other job that someone else has sent. This is suggested
too if you have unfixable older HP Jetdirects; it reduces the
likelihood of the printers wedging.
</P
><P
> To do this, set up a queue on your linux box that points at the
ethernet equipped HP LJ (as above). Now set up all the clients on
your LAN to point at the LPD queue (eg lj-5 in the example above).
</P
><P
> Some HP network printers apparently don't heed the banner page
setting sent by clients; you can turn off their internally
generated banner page by telnetting to the printer, hitting return
twice, typing "banner: 0" followed by "quit". There are other
settings you can change this way, as well; type "?" to see a list.
</P
><P
> The full range of settings can be controlled with HP's <A
HREF="http://www.hp.com/go/webjetadmin"
TARGET="_top"
>webJetAdmin</A
>
software. This package runs as a daemon, and accepts http
requests on a designated port. It serves up forms and Java
applets which can control HP printers on the network. In theory,
it can also control Unix print queues, but it does so using the
rexec service, which is completely unsecure. I don't advise using
that feature.
</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NETWORKED-PRINTERS-APPSOCKET"
>11.5.1. To AppSocket Devices</A
></H3
><A
NAME="AEN2491"
></A
><A
NAME="AEN2493"
></A
><A
NAME="AEN2496"
></A
><A
NAME="AEN2500"
></A
><P
> Some printers (and printer networking "black boxes") support only
a cheesy little non-protocol involving plain TCP connections;
this is sometimes called the "AppSocket" protocol. Notable in
this category are early-model JetDirect (including some
JetDirectEx) cards. Basically, to print to the printer, you must
open a TCP connection to the printer on a specified port
(typically 9100, or 9100, 9101 and 9102 for three-port boxes) and
stuff your print job into it. LPRng has built-in support for
stuffing print jobs into random TCP ports, but with BSD lpd it's
not so easy. The best thing is probably to obtain and use the
little utility called netcat.
</P
><P
> <A
NAME="AEN2505"
></A
>
<A
NAME="AEN2508"
></A
>
A netcat-using PDQ interface would look something like this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>interface tcp-port-0.1 {
help "This is one of the first interfaces supported by standalone
network printers and print servers. The device simply
listens for a TCP connection on a certain port, and sends
data from any connection to the printer.\nThis interface
requires the netcat program (\"nc\")."
required_args "REMOTE_HOST"
argument {
var = "REMOTE_HOST"
desc = "Remote host"
help = "This is IP name or number of the print server."
}
argument {
var = "REMOTE_PORT"
def_value = "9100"
desc = "Remote port"
help = "This is the TCP port number on the print server that the
print job should be sent to. Most JetDirect cards, and
clones, accept jobs on port 9100 (or 9101 for port 2,
etc)."
}
requires "nc"
send_exec { cat $OUTPUT | nc $REMOTE_HOST $REMOTE_PORT }
}</PRE
></TD
></TR
></TABLE
>
</P
><P
> Failing that, it can be implemented, among other ways, in Perl
using the program below. For better performance, use the
program netcat ("nc"), which does much the same thing in a
general purpose way. Most distributions should have netcat
available in prepackaged form.
</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>#!/usr/bin/perl
# Thanks to Dan McLaughlin for writing the original version of this
# script (And to Jim W. Jones for sitting next to Dan when writing me
# for help ;)
$fileName = @ARGV[0];
open(IN,"$fileName") || die "Can't open file $fileName";
$dpi300 = "\x1B*t300R";
$dosCr = "\x1B&k3G";
$ends = "\x0A";
$port = 9100 unless $port;
$them = "bach.sr.hp.com" unless $them;
$AF_INET = 2;
$SOCK_STREAM = 1;
$SIG{'INT'} = 'dokill';
$sockaddr = 'S n a4 x8';
chop($hostname = `hostname`);
($name,$aliases,$proto) = getprotobyname('tcp');
($name,$aliases,$port) = getservbyname($port,'tcp')
unless $port =~ /^\d+$/;;
($name,$aliases,$type,$len,$thisaddr) =
gethostbyname($hostname);
($name,$aliases,$type,$len,$thataddr) = gethostbyname($them);
$this = pack($sockaddr, $AF_INET, 0, $thisaddr);
$that = pack($sockaddr, $AF_INET, $port, $thataddr);
if (socket(S, $AF_INET, $SOCK_STREAM, $proto)) {
# print "socket ok\n";
}
else {
die $!;
}
# Give the socket an address.
if (bind(S, $this)) {
# print "bind ok\n";
}
else {
die $!;
}
# Call up the server.
if (connect(S,$that)) {
# print "connect ok\n";
}
else {
die $!;
}
# Set socket to be command buffered.
select(S); $| = 1; select(STDOUT);
# print S "@PJL ECHO Hi $hostname! $ends";
# print S "@PJL OPMSG DISPLAY=\"Job $whoami\" $ends";
# print S $dpi300;
# Avoid deadlock by forking.
if($child = fork) {
print S $dosCr;
print S $TimesNewR;
while (<IN>) {
print S;
}
sleep 3;
do dokill();
} else {
while(<S>) {
print;
}
}
sub dokill {
kill 9,$child if $child;
}</PRE
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="IF-FOR-REMOTE-PRINTERS"
>11.6. Running an <TT
CLASS="OPTION"
>if</TT
> for remote printers with old
LPDs</A
></H2
><A
NAME="AEN2516"
></A
><A
NAME="AEN2520"
></A
><P
> One oddity of older versions of lpd is that the <TT
CLASS="OPTION"
>if</TT
>
is not run for remote printers. (Versions after 0.43 or so have
the change originated on FreeBSD such that the <TT
CLASS="OPTION"
>if</TT
>
is always run). If you find that you need to run an
<TT
CLASS="OPTION"
>if</TT
> for a remote printer, and it isn't working
with your lpr, you can do so by setting up a double queue and
requeueing the job. As an example, consider this
<TT
CLASS="FILENAME"
>printcap</TT
>:
</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>lj-5:\
:lp=/dev/null:sh:\
:sd=/var/spool/lpd/lj-5:\
:if=/usr/lib/lpd/filter-lj-5:
lj-5-remote:sh:rm=printer.name.com:\
:rp=raw:sd=/var/spool/lpd/lj-5-raw:</PRE
></TD
></TR
></TABLE
>
in light of this <B
CLASS="COMMAND"
>filter-lj-5</B
> script:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>#!/bin/sh
gs <options> -q -dSAFER -sOutputFile=- - | \
lpr -Plj-5-remote -U$5</PRE
></TD
></TR
></TABLE
>
</P
><P
> The <TT
CLASS="OPTION"
>-U</TT
> option to lpr only works if lpr is run
as daemon, and it sets the submitter's name for the job in the
resubmitted queue correctly. You should probably use a more
robust method of getting the username, since in some cases it is
not argument 5. See the man page for <TT
CLASS="FILENAME"
><A
HREF="http://www.linuxprinting.org/man/printcap.5.html"
TARGET="_top"
>printcap</A
></TT
>.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORK-FROM-WINDOWS"
>11.7. From Windows.</A
></H2
><A
NAME="AEN2540"
></A
><A
NAME="AEN2543"
></A
><A
NAME="AEN2547"
></A
><A
NAME="AEN2551"
></A
><P
> Printing from a Windows (or presumably, OS/2) client to a Un*x
server is directly supported over SMB through the use of the
SAMBA package, which also supports file sharing of your Un*x
filesystem to Windows clients.
</P
><P
> Samba includes fairly complete documentation, and there is a good
Samba FAQ which covers it, too. You can either configure a magic
filter on the Un*x box and print PostScript to it, or run around
installing printer-specific drivers on all the Windows machines
and having a queue for them with no filters at all. Relying on
the Windows drivers may in some cases produce better output, but
is a bit more of an administrative hassle if there are many
Windows boxen. So try Postscript first. Modern versions of
Samba should support the automagical driver download mechanism
offered by Windows NT servers to deal with this problem.
</P
><A
NAME="AEN2555"
></A
><P
> With PDQ, you should configure Samba to run the pdq command with
appropriate arguments instead of the lpr command that it defaults
to running. I believe that Samba will run pdq as the proper
user, so it should work well this way. There are several Samba
options that you should adjust to do this:
<P
></P
><DL
><DT
>printcap</DT
><DD
><P
>This should point to a "fake" printcap you whip up listing
available printers. All you need is a short and long name
for each printer, one per line:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="SCREEN"
>lp1|Printer One
lp2|Printer Two
lp3|Printer Three</PRE
></TD
></TR
></TABLE
>
The short name will be used as the printer name for the print
command:
</P
></DD
><DT
>print command</DT
><DD
><P
>This will need to be set to something like <TT
CLASS="LITERAL"
>pdq -P %p %s ; rm
%s</TT
>.
</P
></DD
><DT
>lprm command</DT
><DD
><P
>There doesn't seem to be a good value for this setting at the
moment. PDQ's queued jobs will expire after a time, so if the
printer is totally gone there's no problem. If you just
change your mind, you can use <B
CLASS="COMMAND"
>xpdq</B
> to
cancel jobs, but this is inconvenient from Windows. Just put
a do-nothing command like <B
CLASS="COMMAND"
>true</B
> for now. If
you use <B
CLASS="COMMAND"
>lpd</B
> or LPRng as the back-end, then
a suitable <B
CLASS="COMMAND"
>lprm</B
> command should work. I'm
not sure how Samba would identify the lpr queue entry number
for a pdq-submitted job.
</P
></DD
><DT
>lpq command</DT
><DD
><P
>Again, PDQ doesn't offer a good value to put here.
Distributed systems don't offer a sensible way to see the
queue, but samba-centric centralized server systems want to
have a queue worth examining. Just put a do-nothing command
like <B
CLASS="COMMAND"
>true</B
> for now. If you use LPD or LPRng
as the back-end, then a suitable <B
CLASS="COMMAND"
>lpq</B
>
command should work; you just won't see jobs until they're
done being filtered by PDQ.
</P
></DD
></DL
>
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORKS-FROM-APPLE"
>11.8. From an Apple.</A
></H2
><A
NAME="AEN2585"
></A
><A
NAME="AEN2588"
></A
><A
NAME="AEN2591"
></A
><A
NAME="AEN2593"
></A
><P
> Netatalk supports printing from Apple clients over EtherTalk. See
the <A
HREF="http://thehamptons.com/anders/netatalk/"
TARGET="_top"
>Netatalk
HOWTO Page</A
> for more information.
</P
><P
> Really, though, any modern Mac can print over TCP/IP using the LPD
protocol just fine. UVa provides a very nice <A
HREF="http://www.itc.virginia.edu/desktop/mac/ip_printing/ip_printing.html"
TARGET="_top"
>support page</A
> detailing how to set this up.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="NETWORKS-FROM-NETWARE"
>11.9. From Netware.</A
></H2
><A
NAME="AEN2603"
></A
><A
NAME="AEN2606"
></A
><A
NAME="AEN2609"
></A
><A
NAME="AEN2611"
></A
><P
> The ncpfs package includes a daemon named pserver which can be
used to privide service to a NetWare print queue. From what I
understand, this system requires a Bindery-based NetWare, ie 2.x,
3.x, or 4.x with bindery access enabled.
</P
><P
> For more information on ncpfs and it's pserver program, see <A
HREF="ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/"
TARGET="_top"
>the ncpfs FTP
site</A
>.
</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2619"
>11.10. Networked Printer Administration</A
></H2
><A
NAME="AEN2620"
></A
><A
NAME="AEN2623"
></A
><P
> Most networked printers support some method of remote
administration. Often there are easy-to-use web pages for
configuration. More usefully, there is often support for SNMP
management. Typically you can find out interesting information on
printer status like ink and paper levels, print volumes, and so
forth, and you can usually change certain settings. SNMP printer
control, and a number of other printing-related things, are being
standardized by the IEEE's <A
HREF="http://www.pwg.org/"
TARGET="_top"
>Printer Working Group</A
>
</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="NPADMIN"
>11.10.1. <B
CLASS="COMMAND"
>npadmin</B
></A
></H3
><P
> <A
HREF="http://npadmin.sourceforge.net/"
TARGET="_top"
>Npadmin</A
> is a
command-line program which offers an interface to the common SNMP
functionality of networked printers. It implements the standard
<A
HREF="http://www.ietf.org/rfc/rfc1759.txt"
TARGET="_top"
>Printer
MIB</A
>, as well as a few vendor-proprietary schemes used
mainly for older devices. Both printer-discovery style actions
and various printer status queries are supported.
</P
><P
> npadmin has an excellent <A
HREF="http://npadmin.sourceforge.net/man/"
TARGET="_top"
>man page</A
>, and
precompiled packages are distributed for a number of RPM and dpkg
based distributions.
</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN2636"
>11.10.2. Other SNMP tools</A
></H3
><P
> Besides npadmin, there are a number of SNMP tools that will be
useful. <B
CLASS="COMMAND"
>snmptraplogd</B
> can log SNMP trap
events. This is useful for observing printer jams, out of paper
events, etc; it would be straightforward to retransmit certain
events to a pager, or to send an email.
</P
><P
> While npadmin provides simplified support for many network
printers' SNMP interfaces, some printers may have vendor
extensions which npadmin doesn't know about. In this case, you
can use the CMU SNMP tools, which support arbitrary SNMP GET and
SET operations, as well as walks and the like. With these, and a
bit of work, you can make use of any SNMP feature offered by your
printer's MIB. You may need to obtain a MIB from your vendor to
figure out what all the variables are; sometimes vendors think
that people actually use the proprietary tools they ship.
</P
><P
> VA Linux's <B
CLASS="COMMAND"
><A
HREF="http://sourceforge.net/project/?group_id=3648"
TARGET="_top"
>libprinterconf</A
></B
> includes code to perform
network printer discovery. Printers are identified against a
compiled-in library of printer signatures; at the moment the
library is not large, but does cover many common networked
printer models.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="ghostscript.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="winprinters.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Ghostscript.</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Windows-only printers</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
