os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Adjust whitespace to the structural changes of my previous commit,

Browse source 
translators may ignore this
This commit is contained in:
Gabor Pali 2008-10-24 23:18:46 +00:00
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
Show stats Download patch file Download diff file Expand all files Collapse all files

384
en_US.ISO8859-1/articles/cups/article.sgml
View file

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