[deployment-guide/comm-rel: 53/74] NetInterfaces: add commented s390-specific SUBCHANNELS directive
by dsilas
commit 66395b17a47acd436d880c17dfc9bb5f90fb1064
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Mon Jun 28 15:35:29 2010 +0200
NetInterfaces: add commented s390-specific SUBCHANNELS directive
en-US/Network_Interfaces.xml | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index 3c270b8..66fa939 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -410,6 +410,16 @@ ONBOOT=yes</screen>
</command> is the specified source IP address for outgoing packets.</para>
</listitem>
</varlistentry>
+ <!-- silas: s390 (System z)-specific; not sure whether to include yet...
+ <varlistentry>
+ <term>
+ <command>SUBCHANNELS=<replaceable><read_device_bus_id></replaceable>,<replaceable><write_device_bus_id></replaceable>,<replaceable><data_device_bus_id></replaceable>
+ </command>
+ </term>
+ <listitem>
+ <para>where <replaceable><read_device_bus_id></replaceable> is the </para>
+ </listitem>
+ </varlistentry>-->
<varlistentry>
<term>
<command>USERCTL=<replaceable><answer></replaceable>
13 years, 11 months
[deployment-guide/comm-rel: 52/74] modified the DHCP chapter
by dsilas
commit d9c82b5d88928ed1bf9c41c58c4cf8ee3cf8a9e7
Author: Martin Prpic <mprpic(a)redhat.com>
Date: Mon Jun 28 15:31:10 2010 +0200
modified the DHCP chapter
en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml | 166 +++++++++-----------
1 files changed, 76 insertions(+), 90 deletions(-)
---
diff --git a/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml b/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
index 9b5bffd..976ced2 100644
--- a/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
+++ b/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
@@ -60,11 +60,6 @@
</indexterm>
<para>The first step in configuring a DHCP server is to create the configuration file that stores the network information for the clients. Use this file to declare options and global options for client systems.</para>
<para>The configuration file can contain extra tabs or blank lines for easier formatting. Keywords are case-insensitive and lines beginning with a hash mark (#) are considered comments.</para>
- <para>Two DNS update schemes are currently implemented — the ad-hoc DNS update mode and the interim DHCP-DNS interaction draft update mode. If and when these two are accepted as part of the Internet Engineering Task Force (IETF) standards process, there will be a third mode — the standard DNS update method. You must configure the DNS server for compatibility with these schemes. Version 3.0b2pl11 and previous versions used the ad-hoc mode; however, it has been deprecated. To keep the same behavior, add the following line to the top of the configuration file:</para>
- <screen>ddns-update-style ad-hoc;</screen>
- <para>To use the recommended mode, add the following line to the top of the configuration file:</para>
- <screen>ddns-update-style interim;</screen>
- <para>Refer to the <filename>dhcpd.conf</filename> man page for details about the different modes.</para>
<para>There are two types of statements in the configuration file:</para>
<itemizedlist>
<listitem>
@@ -95,7 +90,7 @@
<para>Instead of changing a DHCP configuration file and restarting the service each time, using the <command>omshell</command> command provides an interactive way to connect to, query, and change the configuration of a DHCP server. By using <command>omshell</command>, all changes can be made while the server is running. For more information on <command>omshell</command>, refer to the <command>omshell</command> man page.</para>
</note>
<para>In <xref
- linkend="subnet"/>, the <filename>routers</filename>, <filename>subnet-mask</filename>, <filename>domain-name</filename>, <filename>domain-name-servers</filename>, and <filename>time-offset</filename> options are used for any <filename>host</filename> statements declared below it.</para>
+ linkend="subnet"/>, the <filename>routers</filename>, <filename>subnet-mask</filename>, <filename>domain-search</filename>, <filename>domain-name-servers</filename>, and <filename>time-offset</filename> options are used for any <filename>host</filename> statements declared below it.</para>
<indexterm
significance="normal">
<primary>DHCP</primary>
@@ -110,13 +105,45 @@
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.254;
option subnet-mask 255.255.255.0;
- option domain-name "example.com";
+ option domain-search "example.com";
option domain-name-servers 192.168.1.1;
option time-offset -18000; # Eastern Standard Time
range 192.168.1.10 192.168.1.100;
}
</screen>
</example>
+ <para>To configure a DHCP server that leases a dynamic IP address to a system within a subnet, modify <xref
+ linkend="dynamic-ip"/> with your values. It declares a default lease time, maximum lease time, and network configuration values for the clients. This example assigns IP addresses in the <filename>range</filename> 192.168.1.10 and 192.168.1.100 to client systems.</para>
+ <example
+ id="dynamic-ip">
+ <title>Range Parameter</title>
+ <screen>
+default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}
+</screen>
+ </example>
+ <para>To assign an IP address to a client based on the MAC address of the network interface card, use the <filename>hardware ethernet</filename> parameter within a <filename>host</filename> declaration. As demonstrated in <xref
+ linkend="static-ip"/>, the <filename>host apex</filename> declaration specifies that the network interface card with the MAC address 00:A0:78:8E:9E:AA always receives the IP address 192.168.1.4.</para>
+ <para>Note that the optional parameter <filename>host-name</filename> can also be used to assign a host name to the client.</para>
+ <example
+ id="static-ip">
+ <title>Static IP Address using DHCP</title>
+ <screen>
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</screen>
+ </example>
<indexterm
significance="normal">
<primary>DHCP</primary>
@@ -131,7 +158,7 @@ subnet 192.168.1.0 netmask 255.255.255.0 {
<title>Shared-network Declaration</title>
<screen>
shared-network name {
- option domain-name "test.redhat.com";
+ option domain-search "test.redhat.com";
option domain-name-servers ns1.redhat.com, ns2.redhat.com;
option routers 192.168.0.254;
more parameters for EXAMPLE shared-network
@@ -160,7 +187,7 @@ shared-network name {
group {
option routers 192.168.1.254;
option subnet-mask 255.255.255.0;
- option domain-name "example.com";
+ option domain-search "example.com";
option domain-name-servers 192.168.1.1;
option time-offset -18000; # Eastern Standard Time
host apex {
@@ -176,38 +203,6 @@ group {
}
</screen>
</example>
- <para>To configure a DHCP server that leases a dynamic IP address to a system within a subnet, modify <xref
- linkend="dynamic-ip"/> with your values. It declares a default lease time, maximum lease time, and network configuration values for the clients. This example assigns IP addresses in the <filename>range</filename> 192.168.1.10 and 192.168.1.100 to client systems.</para>
- <example
- id="dynamic-ip">
- <title>Range Parameter</title>
- <screen>
-default-lease-time 600;
-max-lease-time 7200;
-option subnet-mask 255.255.255.0;
-option broadcast-address 192.168.1.255;
-option routers 192.168.1.254;
-option domain-name-servers 192.168.1.1, 192.168.1.2;
-option domain-name "example.com";
-subnet 192.168.1.0 netmask 255.255.255.0 {
- range 192.168.1.10 192.168.1.100;
-}
-</screen>
- </example>
- <para>To assign an IP address to a client based on the MAC address of the network interface card, use the <filename>hardware ethernet</filename> parameter within a <filename>host</filename> declaration. As demonstrated in <xref
- linkend="static-ip"/>, the <filename>host apex</filename> declaration specifies that the network interface card with the MAC address 00:A0:78:8E:9E:AA always receives the IP address 192.168.1.4.</para>
- <para>Note that the optional parameter <filename>host-name</filename> can also be used to assign a host name to the client.</para>
- <example
- id="static-ip">
- <title>Static IP Address using DHCP</title>
- <screen>
-host apex {
- option host-name "apex.example.com";
- hardware ethernet 00:A0:78:8E:9E:AA;
- fixed-address 192.168.1.4;
-}
-</screen>
- </example>
<note>
<title>Tip</title>
<para>The sample configuration file provided can be used as a starting point and custom configuration options can be added to it. To copy it to the proper location, use the following command:</para>
@@ -320,13 +315,13 @@ DHCPDARGS=eth0
significance="normal">
<primary>DHCP</primary>
<secondary>
- <command>dhcrelay</command>
+ dhcrelay
</secondary>
</indexterm>
<indexterm
significance="normal">
<primary>
- <command>dhcrelay</command>
+ dhcrelay
</primary>
</indexterm>
<para>The DHCP Relay Agent (<command>dhcrelay</command>) allows for the relay of DHCP and BOOTP requests from a subnet with no DHCP server on it to one or more DHCP servers on other subnets.</para>
@@ -348,19 +343,8 @@ DHCPDARGS=eth0
<primary>DHCP</primary>
<secondary>connecting to</secondary>
</indexterm>
- <para
- lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN">
- The first step for configuring a DHCP client is to make sure the kernel recognizes the network interface card. Most cards are recognized during the installation process and the system is configured to use the correct kernel module for the card. If a card is added after installation, <application>Kudzu</application>
- <footnote>
- <para>
- <application>Kudzu</application> is a hardware probing tool run at system boot time to determine what hardware has been added or removed from the system.</para>
- </footnote> will recognize it and prompt you for the proper kernel module (Be sure to check the Hardware Compatibility List at <ulink
- url="http://hardware.redhat.com/hcl/">http://hardware.redhat.com/hcl/</ulink>). If either the installation program or kudzu does not recognize the network card, you can load the correct kernel module (refer to <xref
- linkend="ch-General_Parameters_and_Modules"/> for details).</para>
+
<para>To configure a DHCP client manually, modify the <filename>/etc/sysconfig/network</filename> file to enable networking and the configuration file for each network device in the <filename>/etc/sysconfig/network-scripts</filename> directory. In this directory, each device should have a configuration file named <filename>ifcfg-eth0</filename>, where <filename>eth0</filename> is the network device name.</para>
- <para>The <filename>/etc/sysconfig/network</filename> file should contain the following line:</para>
- <screen>NETWORKING=yes</screen>
- <para>The <computeroutput>NETWORKING</computeroutput> variable must be set to <computeroutput>yes</computeroutput> if you want networking to start at boot time.</para>
<para>The <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> file should contain the following lines:</para>
<screen>
DEVICE=eth0
@@ -372,13 +356,13 @@ ONBOOT=yes
<itemizedlist>
<listitem>
<para>
- <command>DHCP_HOSTNAME</command> — Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in &MAJOROS; does not support this feature.)</para>
+ <literal>DHCP_HOSTNAME</literal> — Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in &MAJOROS; does not support this feature.)</para>
</listitem>
<listitem>
<para>
- <command>PEERDNS=<replaceable><answer></replaceable>
- </command>, where <command><replaceable><answer></replaceable>
- </command> is one of the following:</para>
+ <literal>PEERDNS=<replaceable><answer></replaceable>
+ </literal>, where <literal><replaceable><answer></replaceable>
+ </literal> is one of the following:</para>
<itemizedlist>
<listitem>
<para>
@@ -390,28 +374,6 @@ ONBOOT=yes
</listitem>
</itemizedlist>
</listitem>
- <listitem>
- <para>
- <command>SRCADDR=<replaceable><address></replaceable>
- </command>, where <command><replaceable><address></replaceable>
- </command> is the specified source IP address for outgoing packets.</para>
- </listitem>
- <listitem>
- <para>
- <command>USERCTL=<replaceable><answer></replaceable>
- </command>, where <command><replaceable><answer></replaceable>
- </command> is one of the following:</para>
- <itemizedlist>
- <listitem>
- <para>
- <command>yes</command> — Non-root users are allowed to control this device.</para>
- </listitem>
- <listitem>
- <para>
- <command>no</command> — Non-root users are not allowed to control this device.</para>
- </listitem>
- </itemizedlist>
- </listitem>
</itemizedlist>
<para>If you prefer using a graphical interface, refer to <xref
linkend="ch-Network_Configuration"/> for instructions on using the <application>Network Administration Tool</application> to configure a network interface to use DHCP.</para>
@@ -457,8 +419,7 @@ subnet 172.16.0.0 netmask 255.255.255.0 {
<variablelist>
<varlistentry>
<term>
- <computeroutput>subnet <replaceable>10.0.0.0</replaceable> netmask <replaceable>255.255.255.0</replaceable>
- </computeroutput>
+ <computeroutput>subnet <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable> netmask <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
</term>
<listitem>
<para>A <computeroutput>subnet</computeroutput> declaration is required for every network your DHCP server is serving. Multiple subnets require multiple <computeroutput>subnet</computeroutput> declarations. If the DHCP server does not have a network interface in a range of a <computeroutput>subnet</computeroutput> declaration, the DHCP server does not serve that network.</para>
@@ -477,7 +438,7 @@ dhcpd: Not configured to listen on any interfaces!
</varlistentry>
<varlistentry>
<term>
- <computeroutput>option subnet-mask <replaceable>255.255.255.0</replaceable>;</computeroutput>
+ <computeroutput>option subnet-mask <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>option subnet-mask</computeroutput> option defines a subnet mask, and overrides the <computeroutput>netmask</computeroutput> value in the <computeroutput>subnet</computeroutput> declaration. In simple cases, the subnet and netmask values are the same.</para>
@@ -485,7 +446,7 @@ dhcpd: Not configured to listen on any interfaces!
</varlistentry>
<varlistentry>
<term>
- <computeroutput>option routers <replaceable>10.0.0.1</replaceable>;</computeroutput>
+ <computeroutput>option routers <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>option routers</computeroutput> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.</para>
@@ -493,7 +454,7 @@ dhcpd: Not configured to listen on any interfaces!
</varlistentry>
<varlistentry>
<term>
- <computeroutput>range <replaceable>10.0.0.5 10.0.0.15</replaceable>;</computeroutput>
+ <computeroutput>range <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>range</computeroutput> option specifies the pool of available IP addresses. Systems are assigned an address from the range of specified IP addresses.</para>
@@ -554,15 +515,15 @@ host example1 {
</varlistentry>
<varlistentry>
<term>
- <computeroutput>hardware ethernet <replaceable>00:1A:6B:6A:2E:0B</replaceable>;</computeroutput>
+ <computeroutput>hardware ethernet <replaceable><mac_address></replaceable>;</computeroutput>
</term>
<listitem>
- <para>The <computeroutput>hardware ethernet</computeroutput> option identifies the system. To find this address, run the <command>ifconfig</command> command on the desired system, and look for the <computeroutput>HWaddr</computeroutput> address.</para>
+ <para>The <computeroutput>hardware ethernet</computeroutput> option identifies the system. To find this address, run the <command>ip link</command> command.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
- <computeroutput>fixed-address <replaceable>10.0.0.20</replaceable>;</computeroutput>
+ <computeroutput>fixed-address <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>fixed-address</computeroutput> option assigns a valid IP address to the system specified by the <computeroutput>hardware ethernet</computeroutput> option. This address must be outside the IP address pool specified with the <computeroutput>range</computeroutput> option.</para>
@@ -613,6 +574,31 @@ dhcpd: Configuration file errors encountered -- exiting
<para>This error was caused by having multiple <computeroutput>host interface0</computeroutput> declarations defined in <filename>/etc/dhcp/dhcpd.conf</filename>.</para>
</section>
</section>
+ <section id="s1-dhcp_for_ipv6_dhcpv6">
+ <title>DHCP for IPv6 (DHCPv6)</title>
+ <para>
+ The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and server agents can only operate one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
+ </para>
+ <para>
+ The DHCPv6 server configuration file can be found at <filename>/etc/dhcp/dhcpd6.conf</filename>.
+ </para>
+ <para>
+ The sample server configuration file can be found at <filename>/usr/share/doc/dhcp-<version>/dhcpd6.conf.sample</filename>.
+ </para>
+ <para>
+ To start the DHCPv6 service, use the command <command>/sbin/service dhcpd6 start</command>.
+ </para>
+ <para>
+ A simple DHCPv6 server configuration file can look like this:
+ </para>
+ <screen>
+subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}
+ </screen>
+ </section>
<section
id="s1-dhcp-additional-resources">
<title>Additional Resources</title>
@@ -621,7 +607,7 @@ dhcpd: Configuration file errors encountered -- exiting
<primary>DHCP</primary>
<secondary>additional resources</secondary>
</indexterm>
- <para>For additional configuration options, refer to the following resources.</para>
+ <para>For additional configuration options, refer to <citetitle>The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</citetitle> or the following resources.</para>
<section
id="s2-dhcp-installed-docs">
<title>Installed Documentation</title>
13 years, 11 months
[deployment-guide/comm-rel: 50/74] indexed section Authentication Configuration Tool
by dsilas
commit 8630ce3b0b6dff1432eb1841fab7d06cbcd95080
Author: Martin Prpic <mprpic(a)redhat.com>
Date: Mon Jun 28 11:19:07 2010 +0200
indexed section Authentication Configuration Tool
en-US/Authentication_Configuration.xml | 92 +++++++++++++++++++++++++++++---
1 files changed, 84 insertions(+), 8 deletions(-)
---
diff --git a/en-US/Authentication_Configuration.xml b/en-US/Authentication_Configuration.xml
index 52e9c64..0209f88 100644
--- a/en-US/Authentication_Configuration.xml
+++ b/en-US/Authentication_Configuration.xml
@@ -6,12 +6,16 @@
<section id="sect-The_Authentication_Configuration_Tool">
<title>The Authentication Configuration Tool</title>
<indexterm significance="normal">
- <primary>
- <application>Authentication Configuration Tool</application>
- </primary>
+ <primary>authentication</primary>
+ <secondary>
+ Authentication Configuration Tool
+ </secondary>
</indexterm>
<indexterm significance="normal">
- <primary>authentication</primary>
+ <primary>tool</primary>
+ <secondary>
+ Authentication Configuration Tool
+ </secondary>
</indexterm>
<para>When a user logs in to a &MAJOROS; system, the username and password combination must be verified, or <firstterm>authenticated</firstterm>, as a valid and active user. Sometimes the information to verify the user is located on the local system, and other times the system defers the authentication to a user database on a remote system.</para>
<para>The <application>Authentication Configuration Tool</application> provides a graphical interface for configuring user information retrieval from <firstterm>Lightweight Directory Access Protocol</firstterm> (LDAP), <firstterm> Network Information Service</firstterm> (NIS), and <firstterm>Winbind</firstterm> user account databases. This tool also allows you to configure Kerberos to be used as the authentication protocol when using LDAP or NIS.</para>
@@ -22,18 +26,18 @@
</note>
<indexterm significance="normal">
<primary>
- <command>system-config-authentication</command>
+ system-config-authentication
</primary>
<see>
- <application>Authentication Configuration Tool</application>
+ Authentication Configuration Tool
</see>
</indexterm>
<indexterm significance="normal">
<primary>
- <command>authconfig</command>
+ authconfig
</primary>
<see>
- <application>Authentication Configuration Tool</application>
+ Authentication Configuration Tool
</see>
</indexterm>
<para>To start the graphical version of the <application>Authentication Configuration Tool</application> from the desktop, click <menuchoice><guimenu>System</guimenu> <guimenuitem>Administration</guimenuitem> <guimenuitem>Authentication</guimenuitem></menuchoice> or type the command <command>system-config-authentication</command> at a shell prompt (for example, in an <application>XTerm</application> or a <application>GNOME</application> terminal).</para>
@@ -58,6 +62,14 @@
The following list explains what each option configures:
</para>
<bridgehead>LDAP</bridgehead>
+ <indexterm significance="normal">
+ <primary>
+ Authentication Configuration Tool
+ </primary>
+ <secondary>
+ and LDAP
+ </secondary>
+ </indexterm>
<para>The <guilabel>LDAP</guilabel> option instructs the system to retrieve user information via LDAP. It contains the following specifications:
</para>
<itemizedlist>
@@ -91,6 +103,14 @@
</para>
<itemizedlist>
<listitem>
+ <indexterm significance="normal">
+ <primary>
+ Authentication Configuration Tool
+ </primary>
+ <secondary>
+ and Kerberos authentication
+ </secondary>
+ </indexterm>
<para>
<guilabel>Kerberos password</guilabel> — This option enables Kerberos authentication. It contains the following specifications:
<itemizedlist>
@@ -131,6 +151,14 @@
</para>
</note>
<bridgehead>NIS</bridgehead>
+ <indexterm significance="normal">
+ <primary>
+ Authentication Configuration Tool
+ </primary>
+ <secondary>
+ and NIS
+ </secondary>
+ </indexterm>
<para>
The <guilabel>NIS</guilabel> option configures the system to connect to a NIS server (as an NIS client) for user and password authentication. To configure this option, specify the NIS domain and NIS server. If the NIS server is not specified, the daemon attempts to find it via broadcast.
</para>
@@ -147,12 +175,28 @@
</listitem>
<listitem>
<para>
+ <indexterm significance="normal">
+ <primary>
+ Authentication Configuration Tool
+ </primary>
+ <secondary>
+ and NIS authentication
+ </secondary>
+ </indexterm>
<guilabel>NIS password</guilabel> — This option enables NIS authentication. NIS can provide authentication information to outside processes to authenticate users.
</para>
</listitem>
</itemizedlist>
<bridgehead>Winbind</bridgehead>
+ <indexterm significance="normal">
+ <primary>
+ Authentication Configuration Tool
+ </primary>
+ <secondary>
+ and Winbind
+ </secondary>
+ </indexterm>
<para>The <guilabel>Winbind</guilabel> option configures the system to connect to a Windows Active Directory or a Windows domain controller. User information from the specified directory or domain controller can then be accessed, and server authentication options can be configured. It contains the following specifications:</para>
<itemizedlist>
<listitem>
@@ -205,6 +249,14 @@
<para>For more information about the <command>winbindd</command> service, refer to <xref linkend="s1-samba-daemons"/>.
</para>
+ <indexterm significance="normal">
+ <primary>
+ Authentication Configuration Tool
+ </primary>
+ <secondary>
+ and Winbind authentication
+ </secondary>
+ </indexterm>
<para>
Winbind provides only one method of authentication, <guilabel>Winbind password</guilabel>. This method of authentication uses the options specified in the User Account Configuration of Winbind to connect to a Windows Active Directory or a Windows domain controller.
</para>
@@ -225,6 +277,14 @@
<bridgehead>Local Authentication Options</bridgehead>
<itemizedlist>
<listitem>
+ <indexterm significance="normal">
+ <primary>
+ authentication
+ </primary>
+ <secondary>
+ using fingerprint support
+ </secondary>
+ </indexterm>
<para>
<guilabel>Enable fingerprint reader support</guilabel> — By checking this option, you enable fingerprint authentication to log in by scanning your finger with the fingerprint reader.
</para>
@@ -245,6 +305,14 @@
<guilabel>Create home directories on the first login</guilabel> — When enabled, the user's home directory is automatically created when they log in if it does not already exist.
</para>
<bridgehead>Smart Card Authentication Options</bridgehead>
+ <indexterm significance="normal">
+ <primary>
+ authentication
+ </primary>
+ <secondary>
+ using smart card authentication
+ </secondary>
+ </indexterm>
<para>
<guilabel>Enable smart card support</guilabel> — This option enables smart card authentication. Smart card authentication allows you to log in using a certificate and a key associated with a smart card.
</para>
@@ -289,6 +357,14 @@
</section>
<section id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">
<title>Command Line Version</title>
+ <indexterm significance="normal">
+ <primary>
+ authconfig
+ </primary>
+ <secondary>
+ commands
+ </secondary>
+ </indexterm>
<para>
The <application>Authentication Configuration Tool</application> also supports a command line interface. The command line version can be used in a configuration script or a kickstart script. The authentication options are summarized in <xref linkend="tb-authconfig-cmd-line"/>.
</para>
13 years, 11 months
[deployment-guide/comm-rel: 49/74] Merge branch 'jarek'
by dsilas
commit 502d686a118bc58579ebf039e32b86b72ba1120e
Merge: 08e2a08... 7253c1e...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Fri Jun 25 16:20:07 2010 +0200
Merge branch 'jarek'
.gitignore | 1 +
en-US/Console_Access.xml | 8 +++-----
2 files changed, 4 insertions(+), 5 deletions(-)
---
13 years, 11 months
[deployment-guide/comm-rel: 48/74] Merge branch 'martin'
by dsilas
commit 08e2a086d2d96126cdba499c354edcce28ada923
Merge: d15f31e... 09215b3...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Fri Jun 25 16:20:02 2010 +0200
Merge branch 'martin'
en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml | 28 ++++++++++----------
1 files changed, 14 insertions(+), 14 deletions(-)
---
13 years, 11 months
[deployment-guide/comm-rel: 47/74] (multiple): Fix BZ#598800: Review feedback
by dsilas
commit d15f31e1a8ebb4b284093b98cef5d07976412f29
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Fri Jun 25 15:54:58 2010 +0200
(multiple): Fix BZ#598800: Review feedback
en-US/The_sysconfig_Directory.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_sysconfig_Directory.xml b/en-US/The_sysconfig_Directory.xml
index c289b25..4694002 100644
--- a/en-US/The_sysconfig_Directory.xml
+++ b/en-US/The_sysconfig_Directory.xml
@@ -468,7 +468,7 @@ SYSFONT="latarcyrheb-sun16"
<para>
<command>LOGLEVEL=<replaceable><value></replaceable>
</command>, where <command><replaceable><value></replaceable>
- </command> sets the initial console logging level for the kernel. The default is 3; 8 means everything (including debugging), while 1 means only kernel panics. The <command>syslogd</command> daemon overrides this setting once started.</para>
+ </command> sets the initial console logging level for the kernel. The default is 3; 8 means everything (including debugging), while 1 means only kernel panics. The <command>rsyslog</command> daemon overrides this setting once started.</para>
</listitem>
<listitem>
<para>
13 years, 11 months
[deployment-guide/comm-rel: 45/74] (multiple): Fix BZ#598800: Review feedback
by dsilas
commit 0e73b68305d4b3587cf7eb14c12a1fae62be99ab
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Fri Jun 25 15:52:36 2010 +0200
(multiple): Fix BZ#598800: Review feedback
en-US/Log_Files.xml | 6 +++---
en-US/Samba.xml | 2 +-
en-US/The_BIND_DNS_Server.xml | 6 +++---
3 files changed, 7 insertions(+), 7 deletions(-)
---
diff --git a/en-US/Log_Files.xml b/en-US/Log_Files.xml
index 33de966..3ee944e 100644
--- a/en-US/Log_Files.xml
+++ b/en-US/Log_Files.xml
@@ -23,16 +23,16 @@
significance="normal">
<primary>log files</primary>
<secondary>
- <command>syslogd</command>
+ <command>rsyslod daemon</command>
</secondary>
</indexterm>
<indexterm
significance="normal">
<primary>
- <command>syslogd</command>
+ <command>rsyslog</command>
</primary>
</indexterm>
- <para>Some log files are controlled by a daemon called <command>syslogd</command>. A list of log messages maintained by <command>syslogd</command> can be found in the <filename>/etc/syslog.conf</filename> configuration file.</para>
+ <para>Some log files are controlled by a daemon called <command>rsyslog</command>. A list of log messages maintained by <command>rsyslog</command> can be found in the <filename>/etc/rsyslog.conf</filename> configuration file.</para>
<section
id="s1-logfiles-locating">
<title>Locating Log Files</title>
diff --git a/en-US/Samba.xml b/en-US/Samba.xml
index 4fa157c..bfa2517 100644
--- a/en-US/Samba.xml
+++ b/en-US/Samba.xml
@@ -394,7 +394,7 @@
<itemizedlist>
<listitem>
<para>
- <guilabel>ADS</guilabel> — The Samba server acts as a domain member in an Active Directory Domain (ADS) realm. For this option, Kerberos must be installed and configured on the server, and Samba must become a member of the ADS realm using the <command>net</command> utility, which is part of the <filename>samba-client</filename> package. Refer to the <command>net</command> man page for details. This option does not configure Samba to be an ADS Controller. Specify the realm of the Kerberos server in the <guilabel>Kerberos Realm</guilabel> field.</para>
+ <guilabel>ADS</guilabel> — The Samba server acts as a domain member in an Active Directory Domain (ADS) realm. For this option, Kerberos must be installed and configured on the server, and Samba must become a member of the ADS realm using the <command>net</command> utility, which is part of the <filename>samba-common</filename> package. Refer to the <command>net</command> man page for details. This option does not configure Samba to be an ADS Controller. Specify the realm of the Kerberos server in the <guilabel>Kerberos Realm</guilabel> field.</para>
<note>
<title>Note</title>
<para>The <guilabel>Kerberos Realm</guilabel> field must be supplied in all uppercase letters, such as <command>EXAMPLE.COM</command>.</para>
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index cb4c346..2d36df2 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -251,7 +251,7 @@
<replaceable><statement-1></replaceable> ["<replaceable><statement-1-name></replaceable>"] [<replaceable><statement-1-class></replaceable>] {
<replaceable><option-1></replaceable>;
<replaceable><option-2></replaceable>;
- <replaceable><option-N></replaceable>;
+ <replaceable><option-N></replaceable>;
};
<replaceable><statement-2></replaceable> ["<replaceable><statement-2-name></replaceable>"] [<replaceable><statement-2-class></replaceable>] {
<replaceable><option-1></replaceable>;
@@ -565,7 +565,7 @@ server is a master server for the zone.</para>
<screen>zone <replaceable><zone-name></replaceable>
<replaceable><zone-class></replaceable>
<replaceable><zone-options></replaceable>;
-[<replaceable><zone-options></replaceable>; ...]
+[<replaceable><zone-options></replaceable>; ...]
};</screen>
<para>In this statement, <replaceable><zone-name></replaceable> is the name of the zone, <replaceable><zone-class></replaceable> is the optional class of the zone, and <replaceable><zone-options></replaceable> is a list of options characterizing the zone.</para>
<para>The <replaceable><zone-name></replaceable> attribute for the zone statement is particularly important. It is the default value assigned for the <command>$ORIGIN</command> directive used within the corresponding zone file located in the <filename>/var/named/</filename> directory. The <command>named</command> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file.</para>
@@ -792,7 +792,7 @@ masters { 192.168.0.1; };
</term>
<listitem>
<para>Allows for the use of multiple types of logs, called <firstterm>channels</firstterm>. By using the <command>channel</command> option within the <command>logging</command> statement, a customized type of log can be constructed — with its own file name (<command>file</command>), size limit (<command>size</command>), versioning (<command>version</command>), and level of importance (<command>severity</command>). Once a customized channel <!-- RHEL5: has been -->is defined, a <command>category</command> option is used to categorize the channel and begin logging when <command>named</command> is restarted.</para>
- <para>By default, <command>named</command> logs standard messages to the <command>syslog</command> daemon, which places them in <filename>/var/log/messages</filename>. This occurs because several standard channels are built into BIND with various severity levels, such as <command>default_syslog</command> (which handles informational logging messages) and <command>default_debug</command> (which specifically handles debugging messages). A default category, called <command>default</command>, uses the built-in channels to do normal logging without any special configuration.</para>
+ <para>By default, <command>named</command> logs standard messages to the <command>rsyslog</command> daemon, which places them in <filename>/var/log/messages</filename>. This occurs because several standard channels are built into BIND with various severity levels, such as <command>default_syslog</command> (which handles informational logging messages) and <command>default_debug</command> (which specifically handles debugging messages). A default category, called <command>default</command>, uses the built-in channels to do normal logging without any special configuration.</para>
<!-- RHEL5: ddomingo(a)redhat.com: above <para>replaces following:
<para>By default, <command>named</command> logs standard messages to the <command>syslog</command> daemon, which places them in <filename>/var/log/messages</filename>. This occurs because several standard channels are built into BIND with various severity levels, such as one that handles informational logging messages (<command>default_syslog</command>) and another that specifically handles debugging messages (<command>default_debug</command>). A default category, called <command>default</command>, uses the built-in channels to do normal logging without any special configuration.</para>
-->
13 years, 11 months
[deployment-guide/comm-rel: 44/74] Added files beginning with `#' to .gitignore.
by dsilas
commit 7253c1e3b4b4f2fefafc6ba9ee8e6d3c212c9fbc
Author: Jaromir Hradilek <jhradile(a)redhat.com>
Date: Fri Jun 25 15:43:23 2010 +0200
Added files beginning with `#' to .gitignore.
While they are useful for certain text editors, they are completely
useless for us. This should make them invisible for git.
.gitignore | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 28533e3..daf3114 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@ tmp
*.marks
var/drafts/NetworkManager.html
.*.swp
+\#*
13 years, 11 months