Adjust whitespace to the structural changes of my previous commit,
translators may ignore this
This commit is contained in:
Gabor Pali
parent
e6c2f67803
commit
e30beda162
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=33119
1 changed files with 190 additions and 194 deletions
|
|
@ -57,222 +57,217 @@
|
|||
url="http://www.cups.org/"></ulink>.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="printing-cups-install">
|
||||
<title>Installing the CUPS Print Server</title>
|
||||
<sect1 id="printing-cups-install">
|
||||
<title>Installing the CUPS Print Server</title>
|
||||
|
||||
<para><application>CUPS</application> can be installed from ports
|
||||
or by using a precompiled binary package. To install
|
||||
<application>CUPS</application> from ports, issue the following
|
||||
command from a root terminal:</para>
|
||||
<para><application>CUPS</application> can be installed from ports or
|
||||
by using a precompiled binary package. To install
|
||||
<application>CUPS</application> from ports, issue the following
|
||||
command from a root terminal:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/print/cups && make install clean</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/print/cups && make install clean</userinput></screen>
|
||||
|
||||
<para>To install <application>CUPS</application> using a
|
||||
precompiled binary, issue the following command from a root
|
||||
terminal:</para>
|
||||
<para>To install <application>CUPS</application> using a precompiled
|
||||
binary, issue the following command from a root terminal:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>pkg_add -r cups</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>pkg_add -r cups</userinput></screen>
|
||||
|
||||
<para>Other optional, but recommended, ports or packages are
|
||||
<filename role="package">print/gutenprint-cups</filename> and
|
||||
<filename role="package">print/hplip</filename>, both of which add
|
||||
drivers and utilities for a variety of printers. Once
|
||||
installed, the <application>CUPS</application> configuration
|
||||
files can be found in the directory
|
||||
<filename>/usr/local/etc/cups</filename>.</para>
|
||||
</sect1>
|
||||
<para>Other optional, but recommended, ports or packages are
|
||||
<filename role="package">print/gutenprint-cups</filename> and
|
||||
<filename role="package">print/hplip</filename>, both of which add
|
||||
drivers and utilities for a variety of printers. Once installed,
|
||||
the <application>CUPS</application> configuration files can be
|
||||
found in the directory
|
||||
<filename>/usr/local/etc/cups</filename>.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="printing-cups-configuring-server">
|
||||
<title>Configuring the CUPS Print Server</title>
|
||||
<sect1 id="printing-cups-configuring-server">
|
||||
<title>Configuring the CUPS Print Server</title>
|
||||
|
||||
<para>After installation, a few files must edited in order to
|
||||
configure the <application>CUPS</application> server. First,
|
||||
create or modify, as the case may be, the file
|
||||
<filename>/etc/devfs.rules</filename> and add the following
|
||||
information to set the proper permissions on all potential
|
||||
printer devices and to associate printers with the <groupname>cups</groupname> user
|
||||
group:</para>
|
||||
<para>After installation, a few files must edited in order to
|
||||
configure the <application>CUPS</application> server. First,
|
||||
create or modify, as the case may be, the file
|
||||
<filename>/etc/devfs.rules</filename> and add the following
|
||||
information to set the proper permissions on all potential printer
|
||||
devices and to associate printers with the
|
||||
<groupname>cups</groupname> user group:</para>
|
||||
|
||||
<programlisting>[system=10]
|
||||
<programlisting>[system=10]
|
||||
add path 'unlpt*' mode 0660 group cups
|
||||
add path 'ulpt*' mode 0660 group cups
|
||||
add path 'lpt*' mode 0660 group cups</programlisting>
|
||||
|
||||
<para>Next, add two lines to <filename>/etc/rc.conf</filename>
|
||||
as follows:</para>
|
||||
<para>Next, add two lines to <filename>/etc/rc.conf</filename> as
|
||||
follows:</para>
|
||||
|
||||
<programlisting>cupsd_enable="YES"
|
||||
<programlisting>cupsd_enable="YES"
|
||||
devfs_system_ruleset="system"</programlisting>
|
||||
|
||||
<para>These two entries will start the
|
||||
<application>CUPS</application> print server on boot and invoke
|
||||
the local devfs rule created above, respectively.</para>
|
||||
<para>These two entries will start the
|
||||
<application>CUPS</application> print server on boot and invoke
|
||||
the local devfs rule created above, respectively.</para>
|
||||
|
||||
<para>In order to enable <application>CUPS</application> printing
|
||||
under certain µsoft.windows; clients, the line below
|
||||
should be
|
||||
uncommented in <filename>/usr/local/etc/cups/mime.types</filename>
|
||||
and <filename>/usr/local/etc/cups/mime.convs</filename>:</para>
|
||||
<para>In order to enable <application>CUPS</application> printing
|
||||
under certain µsoft.windows; clients, the line below should
|
||||
be uncommented in
|
||||
<filename>/usr/local/etc/cups/mime.types</filename> and
|
||||
<filename>/usr/local/etc/cups/mime.convs</filename>:</para>
|
||||
|
||||
<programlisting>application/octet-stream</programlisting>
|
||||
<programlisting>application/octet-stream</programlisting>
|
||||
|
||||
<para>Once these changes have been made, the &man.devfs.8; and
|
||||
<application>CUPS</application> systems must both be restarted,
|
||||
either by rebooting the computer or issuing the following two
|
||||
commands in a root terminal:</para>
|
||||
<para>Once these changes have been made, the &man.devfs.8; and
|
||||
<application>CUPS</application> systems must both be restarted,
|
||||
either by rebooting the computer or issuing the following two
|
||||
commands in a root terminal:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/etc/rc.d/devfs restart</userinput>
|
||||
<screen>&prompt.root; <userinput>/etc/rc.d/devfs restart</userinput>
|
||||
&prompt.root; <userinput>/usr/local/etc/rc.d/cupsd restart</userinput></screen>
|
||||
</sect1>
|
||||
|
||||
</sect1>
|
||||
<sect1 id="printing-cups-configuring-printers">
|
||||
<title>Configuring Printers on the CUPS Print Server</title>
|
||||
|
||||
<sect1 id="printing-cups-configuring-printers">
|
||||
<title>Configuring Printers on the CUPS Print Server</title>
|
||||
<para>After the <application>CUPS</application> system has been
|
||||
installed and configured, the administrator can begin configuring
|
||||
the local printers attached to the <application>CUPS</application>
|
||||
print server. This part of the process is very similar, if not
|
||||
identical, to configuring <application>CUPS</application> printers
|
||||
on other &unix;-based operating systems, such as a &linux;
|
||||
distribution.</para>
|
||||
|
||||
<para>After the <application>CUPS</application> system has been
|
||||
installed and configured, the administrator can begin configuring
|
||||
the local printers attached to the
|
||||
<application>CUPS</application> print server. This part of the
|
||||
process is very similar, if not identical, to configuring
|
||||
<application>CUPS</application> printers on other &unix;-based
|
||||
operating systems, such as a &linux; distribution.</para>
|
||||
<para>The primary means for managing and administering the
|
||||
<application>CUPS</application> server is through the web-based
|
||||
interface, which can be found by launching a web browser and
|
||||
entering <ulink url="http://localhost:631"></ulink> in the
|
||||
browser's URL bar. If the <application>CUPS</application> server
|
||||
is on another machine on the network, substitute the server's
|
||||
local <acronym>IP</acronym> addresss for
|
||||
<hostid>localhost</hostid>. The <application>CUPS</application>
|
||||
web interface is fairly self-explanatory, as there are sections
|
||||
for managing printers and print jobs, authorizing users, and more.
|
||||
Additionally, on the right-hand side of the Administration screen
|
||||
are several check-boxes allowing easy access to commonly-changed
|
||||
settings, such as whether to share published printers connected to
|
||||
the system, whether to allow remote administration of the
|
||||
<application>CUPS</application> server, and whether to allow users
|
||||
additional access and privileges to the printers and print
|
||||
jobs.</para>
|
||||
|
||||
<para>The primary means for managing and administering the
|
||||
<application>CUPS</application> server is through the web-based
|
||||
interface, which can be found by launching a web browser and
|
||||
entering <ulink url="http://localhost:631"></ulink> in the
|
||||
browser's URL bar. If the <application>CUPS</application>
|
||||
server is on another machine on the network, substitute the
|
||||
server's local <acronym>IP</acronym> addresss for
|
||||
<hostid>localhost</hostid>. The <application>CUPS</application>
|
||||
web interface is fairly self-explanatory, as there are sections
|
||||
for managing printers and print jobs, authorizing users, and
|
||||
more. Additionally, on the right-hand side of the
|
||||
Administration screen are several check-boxes allowing easy
|
||||
access to commonly-changed settings, such as whether to share
|
||||
published printers connected to the system, whether to allow
|
||||
remote administration of the <application>CUPS</application>
|
||||
server, and whether to allow users additional access and
|
||||
privileges to the printers and print jobs.</para>
|
||||
<para>Adding a printer is generally as easy as clicking <quote>Add
|
||||
Printer</quote> at the Administration screen of the
|
||||
<application>CUPS</application> web interface, or clicking one of
|
||||
the <quote>New Printers Found</quote> buttons also at the
|
||||
Administration screen. When presented with the
|
||||
<quote>Device</quote> drop-down box, simply select the desired
|
||||
locally-attached printer, and then continue through the process.
|
||||
If one has added the <filename
|
||||
role="package">print/gutenprint-cups</filename> or <filename
|
||||
role="package">print/hplip</filename> ports or packages as
|
||||
referenced above, then additional print drivers will be available
|
||||
in the subsequent screens that might provide more stability or
|
||||
features.</para>
|
||||
</sect1>
|
||||
|
||||
<para>Adding a printer is generally as easy as clicking
|
||||
<quote>Add Printer</quote> at the Administration screen of
|
||||
the <application>CUPS</application> web interface, or clicking
|
||||
one of the <quote>New Printers Found</quote> buttons also
|
||||
at the Administration screen. When presented with the
|
||||
<quote>Device</quote> drop-down box, simply select the
|
||||
desired locally-attached printer, and then continue through the
|
||||
process. If one has added the
|
||||
<filename role="package">print/gutenprint-cups</filename> or
|
||||
<filename role="package">print/hplip</filename> ports or packages as
|
||||
referenced above, then additional print drivers will be available
|
||||
in the subsequent screens that might provide more stability or
|
||||
features.</para>
|
||||
</sect1>
|
||||
<sect1 id="printing-cups-clients">
|
||||
<title>Configuring CUPS Clients</title>
|
||||
|
||||
<sect1 id="printing-cups-clients">
|
||||
<title>Configuring CUPS Clients</title>
|
||||
<para>Once the <application>CUPS</application> server has been
|
||||
configured and printers have been added and published to the
|
||||
network, the next step is to configure the clients, or the
|
||||
machines that are going to access the
|
||||
<application>CUPS</application> server. If one has a single
|
||||
desktop machine that is acting as both server and client, then
|
||||
much of this information may not be needed.</para>
|
||||
|
||||
<para>Once the <application>CUPS</application> server has been
|
||||
configured and printers have been added and published to the
|
||||
network, the next step is to configure the clients, or the
|
||||
machines that are going to access the
|
||||
<application>CUPS</application> server. If one has a single
|
||||
desktop machine that is acting as both server and client, then
|
||||
much of this information may not be needed.</para>
|
||||
<sect2 id="printing-cups-clients-unix">
|
||||
<title>&unix; Clients</title>
|
||||
|
||||
<sect2 id="printing-cups-clients-unix">
|
||||
<title>&unix; Clients</title>
|
||||
|
||||
<para><application>CUPS</application> will also need to be
|
||||
installed on your &unix; clients. Once
|
||||
<application>CUPS</application> is installed on the clients,
|
||||
then <application>CUPS</application> printers that are
|
||||
shared across the network are often automatically discovered by
|
||||
the printer managers for various desktop environments such as
|
||||
<application>GNOME</application> or
|
||||
<application>KDE</application>. Alternatively, one can access
|
||||
the local <application>CUPS</application> interface on the
|
||||
client machine at <ulink url="http://localhost:631"></ulink> and
|
||||
click on <quote>Add Printer</quote> in the Administration
|
||||
section. When presented with the <quote>Device</quote>
|
||||
drop-down box, simply select the networked
|
||||
<application>CUPS</application> printer, if it was
|
||||
automatically discovered, or select <literal>ipp</literal> or
|
||||
<literal>http</literal> and enter the <acronym>IPP</acronym> or
|
||||
<acronym>HTTP</acronym> <acronym>URI</acronym> of the networked
|
||||
<application>CUPS</application> printer, usually in one of the
|
||||
two following syntaxes:</para>
|
||||
<para><application>CUPS</application> will also need to be
|
||||
installed on your &unix; clients. Once
|
||||
<application>CUPS</application> is installed on the clients,
|
||||
then <application>CUPS</application> printers that are shared
|
||||
across the network are often automatically discovered by the
|
||||
printer managers for various desktop environments such as
|
||||
<application>GNOME</application> or
|
||||
<application>KDE</application>. Alternatively, one can access
|
||||
the local <application>CUPS</application> interface on the
|
||||
client machine at <ulink url="http://localhost:631"></ulink> and
|
||||
click on <quote>Add Printer</quote> in the Administration
|
||||
section. When presented with the <quote>Device</quote>
|
||||
drop-down box, simply select the networked
|
||||
<application>CUPS</application> printer, if it was automatically
|
||||
discovered, or select <literal>ipp</literal> or
|
||||
<literal>http</literal> and enter the <acronym>IPP</acronym> or
|
||||
<acronym>HTTP</acronym> <acronym>URI</acronym> of the networked
|
||||
<application>CUPS</application> printer, usually in one of the
|
||||
two following syntaxes:</para>
|
||||
|
||||
<programlisting>ipp://<replaceable>server-name-or-ip</replaceable>/printers/<replaceable>printername</replaceable></programlisting>
|
||||
|
||||
<programlisting>http://<replaceable>server-name-or-ip</replaceable>:631/printers/<replaceable>printername</replaceable></programlisting>
|
||||
|
||||
<para>If the <application>CUPS</application> clients have
|
||||
difficulty finding other <application>CUPS</application>
|
||||
printers shared across the network, sometimes it is helpful to
|
||||
add or create a file
|
||||
<filename>/usr/local/etc/cups/client.conf</filename> with a
|
||||
single entry as follows:</para>
|
||||
<para>If the <application>CUPS</application> clients have
|
||||
difficulty finding other <application>CUPS</application>
|
||||
printers shared across the network, sometimes it is helpful to
|
||||
add or create a file
|
||||
<filename>/usr/local/etc/cups/client.conf</filename> with a
|
||||
single entry as follows:</para>
|
||||
|
||||
<programlisting>ServerName <replaceable>server-ip</replaceable></programlisting>
|
||||
<programlisting>ServerName <replaceable>server-ip</replaceable></programlisting>
|
||||
|
||||
<para>In this case, <replaceable>server-ip</replaceable> would be replaced by the local
|
||||
<acronym>IP</acronym> address of the
|
||||
<application>CUPS</application> server on the network.</para>
|
||||
</sect2>
|
||||
<para>In this case, <replaceable>server-ip</replaceable> would be
|
||||
replaced by the local <acronym>IP</acronym> address of the
|
||||
<application>CUPS</application> server on the network.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="printing-cups-clients-windows">
|
||||
<title>&windows; Clients</title>
|
||||
<sect2 id="printing-cups-clients-windows">
|
||||
<title>&windows; Clients</title>
|
||||
|
||||
<para>Versions of &windows; prior to XP did not have the
|
||||
capability to natively network with
|
||||
<acronym>IPP</acronym>-based printers. However, &windowsxp;
|
||||
and later versions do have this capability. Therefore, to
|
||||
add a <application>CUPS</application> printer in these
|
||||
versions of &windows; is quite easy. Generally, the &windows;
|
||||
administrator will run the &windows;
|
||||
<literal>Add Printer</literal> wizard, select <literal>Network
|
||||
Printer</literal> and then enter the <acronym>URI</acronym>
|
||||
in the following syntax:</para>
|
||||
<para>Versions of &windows; prior to XP did not have the
|
||||
capability to natively network with <acronym>IPP</acronym>-based
|
||||
printers. However, &windowsxp; and later versions do have this
|
||||
capability. Therefore, to add a <application>CUPS</application>
|
||||
printer in these versions of &windows; is quite easy.
|
||||
Generally, the &windows; administrator will run the &windows;
|
||||
<literal>Add Printer</literal> wizard, select <literal>Network
|
||||
Printer</literal> and then enter the <acronym>URI</acronym> in
|
||||
the following syntax:</para>
|
||||
|
||||
<programlisting>http://<replaceable>server-name-or-ip</replaceable>:631/printers/<replaceable>printername</replaceable></programlisting>
|
||||
<programlisting>http://<replaceable>server-name-or-ip</replaceable>:631/printers/<replaceable>printername</replaceable></programlisting>
|
||||
|
||||
<para>If one has an older version of &windows; without native
|
||||
<acronym>IPP</acronym> printing support, then the general
|
||||
means of connecting to a <application>CUPS</application>
|
||||
printer is to use
|
||||
<filename role="package">net/samba3</filename> and
|
||||
<application>CUPS</application> together, which is a topic
|
||||
outside the scope of this chapter.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
<para>If one has an older version of &windows; without native
|
||||
<acronym>IPP</acronym> printing support, then the general means
|
||||
of connecting to a <application>CUPS</application> printer is to
|
||||
use <filename role="package">net/samba3</filename> and
|
||||
<application>CUPS</application> together, which is a topic
|
||||
outside the scope of this chapter.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="printing-cups-troubleshooting">
|
||||
<title>CUPS Troubleshooting</title>
|
||||
<sect1 id="printing-cups-troubleshooting">
|
||||
<title>CUPS Troubleshooting</title>
|
||||
|
||||
<para>Difficulties with <application>CUPS</application> often lies
|
||||
in permissions. First, double check the &man.devfs.8;
|
||||
permissions as outlined above. Next, check the actual
|
||||
permissions of the devices created in the file system. It is
|
||||
also helpful to make sure your user is a member of the
|
||||
<groupname>cups</groupname> group. If the permissions check boxes
|
||||
in the Administration section of the
|
||||
<application>CUPS</application> web interface do not seem to be
|
||||
working, another fix might be to manually backup the main
|
||||
<application>CUPS</application> configuration file located at
|
||||
<filename>/usr/local/etc/cups/cupsd.conf</filename> and edit the
|
||||
various configuration options and try different combinations of
|
||||
configuration options. One sample
|
||||
<filename>/usr/local/etc/cups/cupsd.conf</filename> to test is
|
||||
listed below. Please note that this sample
|
||||
<filename>cupsd.conf</filename> file sacrifices security for
|
||||
easier configuration; once the administrator successfully
|
||||
connnects to the <application>CUPS</application> server and
|
||||
configures the clients, it is advisable to revisit this
|
||||
configuration file and begin locking down access.</para>
|
||||
<para>Difficulties with <application>CUPS</application> often lies
|
||||
in permissions. First, double check the &man.devfs.8; permissions
|
||||
as outlined above. Next, check the actual permissions of the
|
||||
devices created in the file system. It is also helpful to make
|
||||
sure your user is a member of the <groupname>cups</groupname>
|
||||
group. If the permissions check boxes in the Administration
|
||||
section of the <application>CUPS</application> web interface do
|
||||
not seem to be working, another fix might be to manually backup
|
||||
the main <application>CUPS</application> configuration file
|
||||
located at <filename>/usr/local/etc/cups/cupsd.conf</filename> and
|
||||
edit the various configuration options and try different
|
||||
combinations of configuration options. One sample
|
||||
<filename>/usr/local/etc/cups/cupsd.conf</filename> to test is
|
||||
listed below. Please note that this sample
|
||||
<filename>cupsd.conf</filename> file sacrifices security for
|
||||
easier configuration; once the administrator successfully
|
||||
connnects to the <application>CUPS</application> server and
|
||||
configures the clients, it is advisable to revisit this
|
||||
configuration file and begin locking down access.</para>
|
||||
|
||||
<programlisting># Log general information in error_log - change "info" to "debug" for
|
||||
<programlisting># Log general information in error_log - change "info" to "debug" for
|
||||
# troubleshooting...
|
||||
LogLevel info
|
||||
|
||||
|
|
@ -351,32 +346,33 @@ CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default>
|
|||
Order deny,allow
|
||||
</Limit>
|
||||
</Policy></programlisting>
|
||||
</sect1>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="printing-cups-ports-knobs">
|
||||
<title>Fine Tuning CUPS-Related Ports</title>
|
||||
<sect1 id="printing-cups-ports-knobs">
|
||||
<title>Fine Tuning CUPS-Related Ports</title>
|
||||
|
||||
<para>If <application>CUPS</application> is going to serve as the
|
||||
primary printing system, then one may choose to optionally add
|
||||
certain knobs to <filename>/etc/make.conf</filename> that will
|
||||
emphasize <application>CUPS</application> over other printing
|
||||
options. Some of these <quote>knobs</quote> that one may want to add
|
||||
are:</para>
|
||||
<para>If <application>CUPS</application> is going to serve as the
|
||||
primary printing system, then one may choose to optionally add
|
||||
certain knobs to <filename>/etc/make.conf</filename> that will
|
||||
emphasize <application>CUPS</application> over other printing
|
||||
options. Some of these <quote>knobs</quote> that one may want to
|
||||
add are:</para>
|
||||
|
||||
<programlisting>WITH_CUPS=YES
|
||||
<programlisting>WITH_CUPS=YES
|
||||
CUPS_OVERWRITE_BASE=YES
|
||||
WITHOUT_LPR=YES</programlisting>
|
||||
|
||||
<para>The first knob, <makevar>WITH_CUPS</makevar>, adds
|
||||
<application>CUPS</application> support to ports where
|
||||
applicable. The second knob, <makevar>CUPS_OVERWRITE_BASE</makevar>, will fix
|
||||
certain symlinks and paths that would otherwise apply to the
|
||||
default &os; printing system, <application>LPR</application>,
|
||||
and will prevent these fixes from being reverted upon the next
|
||||
<maketarget>buildworld</maketarget> system upgrade. The third knob, <makevar>WITHOUT_LPR</makevar>, will
|
||||
prevent <application>LPR</application> support from being added
|
||||
to ports where applicable.</para>
|
||||
</sect1>
|
||||
<para>The first knob, <makevar>WITH_CUPS</makevar>, adds
|
||||
<application>CUPS</application> support to ports where applicable.
|
||||
The second knob, <makevar>CUPS_OVERWRITE_BASE</makevar>, will fix
|
||||
certain symlinks and paths that would otherwise apply to the
|
||||
default &os; printing system, <application>LPR</application>, and
|
||||
will prevent these fixes from being reverted upon the next
|
||||
<maketarget>buildworld</maketarget> system upgrade. The third
|
||||
knob, <makevar>WITHOUT_LPR</makevar>, will prevent
|
||||
<application>LPR</application> support from being added to ports
|
||||
where applicable.</para>
|
||||
</sect1>
|
||||
</article>
|
||||
|
||||
<!--
|
||||
|
|
|
|||
Loading…
Reference in a new issue