[SCM] Samba Shared Repository - branch v4-0-test updated
Karolin Seeger
kseeger at samba.org
Wed May 29 05:39:05 MDT 2013
The branch, v4-0-test has been updated
via 2aee249 build: Install smbtar in waf build
via 06228ec build: Blacklist the release-4-0-0 provision as well
via 1100bf2 build: Do not set PATH in install_with_python now we set $PYTHON
via 7f88d81 build: Rework BSD_STYLE_STATVFS check to match autoconf build
via f27239b lib/replace: Set BROKEN_STRNLEN and BROKEN_STRNDUP on all AIX
via 85db5bf docs: Remove all references to testprns
via b54aed1 docs: Fix small errors in TOSHARG-Compiling
via 68c5915 docs: Remove TOSHARG-HighAvailability which is made obsolete by CTDB
via 5bbcf09 docs: Remove out of date and unmaintained Speed page from the HOWTO
from 07073fb dns: Add support for MX queries
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v4-0-test
- Log -----------------------------------------------------------------
commit 2aee249f05cc48e4afe4190b86a8ca4e85101735
Author: Andrew Bartlett <abartlet at samba.org>
Date: Sun May 26 21:05:12 2013 +1000
build: Install smbtar in waf build
Reviewed-by: Kai Blin <kai at samba.org>
Autobuild-User(master): Andrew Bartlett <abartlet at samba.org>
Autobuild-Date(master): Mon May 27 12:55:05 CEST 2013 on sn-devel-104
(cherry picked from commit 1754b52204563a722920805b76e6c571d0268434)
The last 5 patches address bug #9907 - build fixes for 4.0 found during autoconf
or debian packaging work.
Autobuild-User(v4-0-test): Karolin Seeger <kseeger at samba.org>
Autobuild-Date(v4-0-test): Wed May 29 13:38:55 CEST 2013 on sn-devel-104
commit 06228ec70849d839d9c7ec0d40ee6430e9ac912f
Author: Andrew Bartlett <abartlet at samba.org>
Date: Fri Apr 26 16:44:00 2013 +1000
build: Blacklist the release-4-0-0 provision as well
This reduces the size of the published tarball while ensuring we test with it
during autobuild.
Andrew Bartlett
Reviewed-by: Stefan Metzmacher <metze at samba.org>
(cherry picked from commit 768c3bb16ae8aac2d96d4fa0d8a7593fc9be6ca8)
commit 1100bf2cc38850dbcb8f735c7490a6215a71255a
Author: Andrew Bartlett <abartlet at samba.org>
Date: Wed May 8 12:59:05 2013 +1200
build: Do not set PATH in install_with_python now we set $PYTHON
This will ensure that the scripts get rewritten to use this specific python, as it
will not be found in the path by the waf scripts.
Andrew Bartlett
Reviewed-by: Stefan Metzmacher <metze at samba.org>
(cherry picked from commit 20445415307ae3d6524995d0128862dcbc119684)
commit 7f88d819f7d17eab7a2ea3bd4f4848554569a28f
Author: Andrew Bartlett <abartlet at samba.org>
Date: Wed May 22 00:14:29 2013 +1000
build: Rework BSD_STYLE_STATVFS check to match autoconf build
Reviewed-by: Jelmer Vernooij <jelmer at samba.org>
(cherry picked from commit 2a4eaa3241fc4ccb79359ea4e4d511754a84d46b)
commit f27239b8e9a2a4994a09eb45da6a7e8edf8b35b0
Author: Andrew Bartlett <abartlet at samba.org>
Date: Wed May 22 17:23:30 2013 +1000
lib/replace: Set BROKEN_STRNLEN and BROKEN_STRNDUP on all AIX
The background is in https://bugzilla.samba.org/show_bug.cgi?id=1097
and wider reports are at
http://stackoverflow.com/questions/2091460/strndup-call-is-currupting-stack-frames
Reviewed-by: Jeremy Allison <jra at samba.org>
Autobuild-User(master): Jeremy Allison <jra at samba.org>
Autobuild-Date(master): Thu May 23 03:52:10 CEST 2013 on sn-devel-104
(cherry picked from commit 9ddfd7d8784e6f546628f48990b69ee2850be52d)
commit 85db5bf64cb5ada803d244195c231af479b69a60
Author: Andrew Bartlett <abartlet at samba.org>
Date: Sun May 26 20:29:19 2013 +1000
docs: Remove all references to testprns
Based on debian patch documentation2.patch by Christian Perrier <bubulle at debian.org>.
This tool no longer exists in Samba.
Andrew Bartlett
Reviewed-by: Kai Blin <kai at samba.org>
(cherry picked from commit 4ae3cdcd7151237a858f668357d08ab6916bdb3b)
The last 4 patches address bug #9906 - Doc fixes for 4.0.
commit b54aed1cb1bf5750f26f1962180217443b72a8b0
Author: Andrew Bartlett <abartlet at samba.org>
Date: Tue May 21 20:44:26 2013 +1000
docs: Fix small errors in TOSHARG-Compiling
Reviewed-by: Jeremy Allison <jra at samba.org>
(cherry picked from commit e896f3c5bf5dee3c771985cd9dd2eb376481c22b)
commit 68c591573139504840689c942e5ba064f92fc7d9
Author: Andrew Bartlett <abartlet at samba.org>
Date: Tue May 21 20:50:30 2013 +1000
docs: Remove TOSHARG-HighAvailability which is made obsolete by CTDB
This is mostly a lament on why this is hard, and while CTDB is still
hard, this document tries to imply it is almost impossible, and makes
no mention of the solution.
Andrew Bartlett
Reviewed-by: Jeremy Allison <jra at samba.org>
(cherry picked from commit f632150e1b5a8d8a32753f43f7433b392f3a2136)
commit 5bbcf09faa29747ebbc90cb6b17e6ba75a9ebe58
Author: Andrew Bartlett <abartlet at samba.org>
Date: Tue May 21 17:49:55 2013 +1000
docs: Remove out of date and unmaintained Speed page from the HOWTO
Reviewed-by: Jeremy Allison <jra at samba.org>
(cherry picked from commit fa8e760882ea389f8c94d6dfdc7386b0295974d1)
-----------------------------------------------------------------------
Summary of changes:
docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml | 6 +-
docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml | 500 --------------------
docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml | 327 -------------
docs-xml/Samba3-HOWTO/index.xml | 4 -
docs-xml/manpages/nmbd.8.xml | 1 -
docs-xml/manpages/smb.conf.5.xml | 1 -
docs-xml/manpages/smbd.8.xml | 1 -
docs-xml/using_samba/appd.xml | 18 -
docs-xml/using_samba/ch01.xml | 6 -
docs-xml/using_samba/ch07.xml | 8 -
examples/tridge/smb.conf | 8 -
install_with_python.sh | 2 -
lib/replace/wscript | 13 +
lib/util/wscript_configure | 22 +-
source3/script/wscript_build | 7 +
source3/wscript_build | 1 +
wscript | 2 +-
17 files changed, 35 insertions(+), 892 deletions(-)
delete mode 100644 docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml
delete mode 100644 docs-xml/Samba3-HOWTO/TOSHARG-Speed.xml
create mode 100644 source3/script/wscript_build
Changeset truncated at 500 lines:
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml
index ac866a8..3a2b729 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-Compiling.xml
@@ -119,7 +119,7 @@ gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
<para>
<indexterm><primary>configure</primary></indexterm>
To build the binaries, run the program <userinput>./configure
- </userinput> in the top level director of the source tree. This should automatically
+ </userinput> in the top level directory of the source tree. This should automatically
configure Samba for your operating system. If you have unusual
needs, then you may wish to first run:
<screen>
@@ -177,7 +177,7 @@ gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
<para>
After you run configure, make sure that the
- <filename>bin/include/config.h</filename> it generates contain lines like this:
+ <filename>bin/default/include/config.h</filename> it generates contain lines like this:
<programlisting>
#define HAVE_KRB5 1
#define HAVE_LDAP 1
@@ -186,7 +186,7 @@ gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
<para>
If it does not, configure did not find your KRB5 libraries or
- your LDAP libraries. Look in <filename>config.log</filename> to figure
+ your LDAP libraries. Look in <filename>bin/config.log</filename> to figure
out why and fix it.
</para>
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml b/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml
deleted file mode 100644
index 1ce81d4..0000000
--- a/docs-xml/Samba3-HOWTO/TOSHARG-HighAvailability.xml
+++ /dev/null
@@ -1,500 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="SambaHA">
-<chapterinfo>
- &author.jht;
- &author.jeremy;
-</chapterinfo>
-
-<title>High Availability</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>availability</primary></indexterm>
-<indexterm><primary>intolerance</primary></indexterm>
-<indexterm><primary>vital task</primary></indexterm>
-Network administrators are often concerned about the availability of file and print
-services. Network users are inclined toward intolerance of the services they depend
-on to perform vital task responsibilities.
-</para>
-
-<para>
-A sign in a computer room served to remind staff of their responsibilities. It read:
-</para>
-
-<blockquote>
-<para>
-<indexterm><primary>fail</primary></indexterm>
-<indexterm><primary>managed by humans</primary></indexterm>
-<indexterm><primary>economically wise</primary></indexterm>
-<indexterm><primary>anticipate failure</primary></indexterm>
-All humans fail, in both great and small ways we fail continually. Machines fail too.
-Computers are machines that are managed by humans, the fallout from failure
-can be spectacular. Your responsibility is to deal with failure, to anticipate it
-and to eliminate it as far as is humanly and economically wise to achieve.
-Are your actions part of the problem or part of the solution?
-</para>
-</blockquote>
-
-<para>
-If we are to deal with failure in a planned and productive manner, then first we must
-understand the problem. That is the purpose of this chapter.
-</para>
-
-<para>
-<indexterm><primary>high availability</primary></indexterm>
-<indexterm><primary>CIFS/SMB</primary></indexterm>
-<indexterm><primary>state of knowledge</primary></indexterm>
-Parenthetically, in the following discussion there are seeds of information on how to
-provision a network infrastructure against failure. Our purpose here is not to provide
-a lengthy dissertation on the subject of high availability. Additionally, we have made
-a conscious decision to not provide detailed working examples of high availability
-solutions; instead we present an overview of the issues in the hope that someone will
-rise to the challenge of providing a detailed document that is focused purely on
-presentation of the current state of knowledge and practice in high availability as it
-applies to the deployment of Samba and other CIFS/SMB technologies.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Technical Discussion</title>
-
-<para>
-<indexterm><primary>SambaXP conference</primary></indexterm>
-<indexterm><primary>Germany</primary></indexterm>
-<indexterm><primary>inspired structure</primary></indexterm>
-The following summary was part of a presentation by Jeremy Allison at the SambaXP 2003
-conference that was held at Goettingen, Germany, in April 2003. Material has been added
-from other sources, but it was Jeremy who inspired the structure that follows.
-</para>
-
- <sect2>
- <title>The Ultimate Goal</title>
-
- <para>
-<indexterm><primary>clustering technologies</primary></indexterm>
-<indexterm><primary>affordable power</primary></indexterm>
-<indexterm><primary>unstoppable services</primary></indexterm>
- All clustering technologies aim to achieve one or more of the following:
- </para>
-
- <itemizedlist>
- <listitem><para>Obtain the maximum affordable computational power.</para></listitem>
- <listitem><para>Obtain faster program execution.</para></listitem>
- <listitem><para>Deliver unstoppable services.</para></listitem>
- <listitem><para>Avert points of failure.</para></listitem>
- <listitem><para>Exact most effective utilization of resources.</para></listitem>
- </itemizedlist>
-
- <para>
- A clustered file server ideally has the following properties:
-<indexterm><primary>clustered file server</primary></indexterm>
-<indexterm><primary>connect transparently</primary></indexterm>
-<indexterm><primary>transparently reconnected</primary></indexterm>
-<indexterm><primary>distributed file system</primary></indexterm>
- </para>
-
- <itemizedlist>
- <listitem><para>All clients can connect transparently to any server.</para></listitem>
- <listitem><para>A server can fail and clients are transparently reconnected to another server.</para></listitem>
- <listitem><para>All servers serve out the same set of files.</para></listitem>
- <listitem><para>All file changes are immediately seen on all servers.</para>
- <itemizedlist><listitem><para>Requires a distributed file system.</para></listitem></itemizedlist></listitem>
- <listitem><para>Infinite ability to scale by adding more servers or disks.</para></listitem>
- </itemizedlist>
-
- </sect2>
-
- <sect2>
- <title>Why Is This So Hard?</title>
-
- <para>
- In short, the problem is one of <emphasis>state</emphasis>.
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
-<indexterm><primary>state information</primary></indexterm>
- All TCP/IP connections are dependent on state information.
- </para>
- <para>
-<indexterm><primary>TCP failover</primary></indexterm>
- The TCP connection involves a packet sequence number. This
- sequence number would need to be dynamically updated on all
- machines in the cluster to effect seamless TCP failover.
- </para>
- </listitem>
- <listitem>
- <para>
-<indexterm><primary>CIFS/SMB</primary></indexterm>
-<indexterm><primary>TCP</primary></indexterm>
- CIFS/SMB (the Windows networking protocols) uses TCP connections.
- </para>
- <para>
- This means that from a basic design perspective, failover is not
- seriously considered.
- <itemizedlist>
- <listitem><para>
- All current SMB clusters are failover solutions
- &smbmdash; they rely on the clients to reconnect. They provide server
- failover, but clients can lose information due to a server failure.
-<indexterm><primary>server failure</primary></indexterm>
- </para></listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Servers keep state information about client connections.
- <itemizedlist>
-<indexterm><primary>state</primary></indexterm>
- <listitem><para>CIFS/SMB involves a lot of state.</para></listitem>
- <listitem><para>Every file open must be compared with other open files
- to check share modes.</para></listitem>
- </itemizedlist>
- </para>
- </listitem>
- </itemizedlist>
-
- <sect3>
- <title>The Front-End Challenge</title>
-
- <para>
-<indexterm><primary>cluster servers</primary></indexterm>
-<indexterm><primary>single server</primary></indexterm>
-<indexterm><primary>TCP data streams</primary></indexterm>
-<indexterm><primary>front-end virtual server</primary></indexterm>
-<indexterm><primary>virtual server</primary></indexterm>
-<indexterm><primary>de-multiplex</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
- To make it possible for a cluster of file servers to appear as a single server that has one
- name and one IP address, the incoming TCP data streams from clients must be processed by the
- front-end virtual server. This server must de-multiplex the incoming packets at the SMB protocol
- layer level and then feed the SMB packet to different servers in the cluster.
- </para>
-
- <para>
-<indexterm><primary>IPC$ connections</primary></indexterm>
-<indexterm><primary>RPC calls</primary></indexterm>
- One could split all IPC$ connections and RPC calls to one server to handle printing and user
- lookup requirements. RPC printing handles are shared between different IPC4 sessions &smbmdash; it is
- hard to split this across clustered servers!
- </para>
-
- <para>
- Conceptually speaking, all other servers would then provide only file services. This is a simpler
- problem to concentrate on.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Demultiplexing SMB Requests</title>
-
- <para>
-<indexterm><primary>SMB requests</primary></indexterm>
-<indexterm><primary>SMB state information</primary></indexterm>
-<indexterm><primary>front-end virtual server</primary></indexterm>
-<indexterm><primary>complicated problem</primary></indexterm>
- De-multiplexing of SMB requests requires knowledge of SMB state information,
- all of which must be held by the front-end <emphasis>virtual</emphasis> server.
- This is a perplexing and complicated problem to solve.
- </para>
-
- <para>
-<indexterm><primary>vuid</primary></indexterm>
-<indexterm><primary>tid</primary></indexterm>
-<indexterm><primary>fid</primary></indexterm>
- Windows XP and later have changed semantics so state information (vuid, tid, fid)
- must match for a successful operation. This makes things simpler than before and is a
- positive step forward.
- </para>
-
- <para>
-<indexterm><primary>SMB requests</primary></indexterm>
-<indexterm><primary>Terminal Server</primary></indexterm>
- SMB requests are sent by vuid to their associated server. No code exists today to
- effect this solution. This problem is conceptually similar to the problem of
- correctly handling requests from multiple requests from Windows 2000
- Terminal Server in Samba.
- </para>
-
- <para>
-<indexterm><primary>de-multiplexing</primary></indexterm>
- One possibility is to start by exposing the server pool to clients directly.
- This could eliminate the de-multiplexing step.
- </para>
-
- </sect3>
-
- <sect3>
- <title>The Distributed File System Challenge</title>
-
- <para>
-<indexterm><primary>Distributed File Systems</primary></indexterm>
- There exists many distributed file systems for UNIX and Linux.
- </para>
-
- <para>
-<indexterm><primary>backend</primary></indexterm>
-<indexterm><primary>SMB semantics</primary></indexterm>
-<indexterm><primary>share modes</primary></indexterm>
-<indexterm><primary>locking</primary></indexterm>
-<indexterm><primary>oplock</primary></indexterm>
-<indexterm><primary>distributed file systems</primary></indexterm>
- Many could be adopted to backend our cluster, so long as awareness of SMB
- semantics is kept in mind (share modes, locking, and oplock issues in particular).
- Common free distributed file systems include:
-<indexterm><primary>NFS</primary></indexterm>
-<indexterm><primary>AFS</primary></indexterm>
-<indexterm><primary>OpenGFS</primary></indexterm>
-<indexterm><primary>Lustre</primary></indexterm>
- </para>
-
- <itemizedlist>
- <listitem><para>NFS</para></listitem>
- <listitem><para>AFS</para></listitem>
- <listitem><para>OpenGFS</para></listitem>
- <listitem><para>Lustre</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>server pool</primary></indexterm>
- The server pool (cluster) can use any distributed file system backend if all SMB
- semantics are performed within this pool.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Restrictive Constraints on Distributed File Systems</title>
-
- <para>
-<indexterm><primary>SMB services</primary></indexterm>
-<indexterm><primary>oplock handling</primary></indexterm>
-<indexterm><primary>server pool</primary></indexterm>
-<indexterm><primary>backend file system pool</primary></indexterm>
- Where a clustered server provides purely SMB services, oplock handling
- may be done within the server pool without imposing a need for this to
- be passed to the backend file system pool.
- </para>
-
- <para>
-<indexterm><primary>NFS</primary></indexterm>
-<indexterm><primary>interoperability</primary></indexterm>
- On the other hand, where the server pool also provides NFS or other file services,
- it will be essential that the implementation be oplock-aware so it can
- interoperate with SMB services. This is a significant challenge today. A failure
- to provide this interoperability will result in a significant loss of performance that will be
- sorely noted by users of Microsoft Windows clients.
- </para>
-
- <para>
- Last, all state information must be shared across the server pool.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Server Pool Communications</title>
-
- <para>
-<indexterm><primary>POSIX semantics</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>POSIX locks</primary></indexterm>
-<indexterm><primary>SMB locks</primary></indexterm>
- Most backend file systems support POSIX file semantics. This makes it difficult
- to push SMB semantics back into the file system. POSIX locks have different properties
- and semantics from SMB locks.
- </para>
-
- <para>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>tdb</primary></indexterm>
-<indexterm><primary>Clustered smbds</primary></indexterm>
- All <command>smbd</command> processes in the server pool must of necessity communicate
- very quickly. For this, the current <parameter>tdb</parameter> file structure that Samba
- uses is not suitable for use across a network. Clustered <command>smbd</command>s must use something else.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Server Pool Communications Demands</title>
-
- <para>
- High-speed interserver communications in the server pool is a design prerequisite
- for a fully functional system. Possibilities for this include:
- </para>
-
- <itemizedlist>
-<indexterm><primary>Myrinet</primary></indexterm>
-<indexterm><primary>scalable coherent interface</primary><see>SCI</see></indexterm>
- <listitem><para>
- Proprietary shared memory bus (example: Myrinet or SCI [scalable coherent interface]).
- These are high-cost items.
- </para></listitem>
-
- <listitem><para>
- Gigabit Ethernet (now quite affordable).
- </para></listitem>
-
- <listitem><para>
- Raw Ethernet framing (to bypass TCP and UDP overheads).
- </para></listitem>
- </itemizedlist>
-
- <para>
- We have yet to identify metrics for performance demands to enable this to happen
- effectively.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Required Modifications to Samba</title>
-
- <para>
- Samba needs to be significantly modified to work with a high-speed server interconnect
- system to permit transparent failover clustering.
- </para>
-
- <para>
- Particular functions inside Samba that will be affected include:
- </para>
-
- <itemizedlist>
- <listitem><para>
- The locking database, oplock notifications,
- and the share mode database.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>failure semantics</primary></indexterm>
-<indexterm><primary>oplock messages</primary></indexterm>
- Failure semantics need to be defined. Samba behaves the same way as Windows.
- When oplock messages fail, a file open request is allowed, but this is
- potentially dangerous in a clustered environment. So how should interserver
- pool failure semantics function, and how should such functionality be implemented?
- </para></listitem>
-
- <listitem><para>
- Should this be implemented using a point-to-point lock manager, or can this
- be done using multicast techniques?
- </para></listitem>
-
- </itemizedlist>
-
- </sect3>
- </sect2>
-
- <sect2>
- <title>A Simple Solution</title>
-
- <para>
-<indexterm><primary>failover servers</primary></indexterm>
-<indexterm><primary>exported file system</primary></indexterm>
-<indexterm><primary>distributed locking protocol</primary></indexterm>
- Allowing failover servers to handle different functions within the exported file system
- removes the problem of requiring a distributed locking protocol.
- </para>
-
- <para>
-<indexterm><primary>high-speed server interconnect</primary></indexterm>
-<indexterm><primary>complex file name space</primary></indexterm>
- If only one server is active in a pair, the need for high-speed server interconnect is avoided.
- This allows the use of existing high-availability solutions, instead of inventing a new one.
- This simpler solution comes at a price &smbmdash; the cost of which is the need to manage a more
- complex file name space. Since there is now not a single file system, administrators
- must remember where all services are located &smbmdash; a complexity not easily dealt with.
- </para>
-
- <para>
-<indexterm><primary>virtual server</primary></indexterm>
- The <emphasis>virtual server</emphasis> is still needed to redirect requests to backend
- servers. Backend file space integrity is the responsibility of the administrator.
- </para>
-
- </sect2>
-
- <sect2>
- <title>High-Availability Server Products</title>
-
- <para>
-<indexterm><primary>resource failover</primary></indexterm>
-<indexterm><primary>high-availability services</primary></indexterm>
-<indexterm><primary>dedicated heartbeat</primary></indexterm>
-<indexterm><primary>LAN</primary></indexterm>
-<indexterm><primary>failover process</primary></indexterm>
- Failover servers must communicate in order to handle resource failover. This is essential
- for high-availability services. The use of a dedicated heartbeat is a common technique to
- introduce some intelligence into the failover process. This is often done over a dedicated
- link (LAN or serial).
- </para>
-
- <para>
-<indexterm><primary>SCSI</primary></indexterm>
-<indexterm><primary>Red Hat Cluster Manager</primary></indexterm>
-<indexterm><primary>Microsoft Wolfpack</primary></indexterm>
-<indexterm><primary>Fiber Channel</primary></indexterm>
-<indexterm><primary>failover communication</primary></indexterm>
- Many failover solutions (like Red Hat Cluster Manager and Microsoft Wolfpack)
- can use a shared SCSI of Fiber Channel disk storage array for failover communication.
- Information regarding Red Hat high availability solutions for Samba may be obtained from
- <ulink url="http://www.redhat.com/docs/manuals/enterprise/RHEL-AS-2.1-Manual/cluster-manager/s1-service-samba.html">www.redhat.com</ulink>.
- </para>
-
- <para>
-<indexterm><primary>Linux High Availability project</primary></indexterm>
- The Linux High Availability project is a resource worthy of consultation if your desire is
- to build a highly available Samba file server solution. Please consult the home page at
- <ulink url="http://www.linux-ha.org/">www.linux-ha.org/</ulink>.
- </para>
-
- <para>
-<indexterm><primary>backend failures</primary></indexterm>
-<indexterm><primary>continuity of service</primary></indexterm>
- Front-end server complexity remains a challenge for high availability because it must deal
- gracefully with backend failures, while at the same time providing continuity of service
- to all network clients.
--
Samba Shared Repository
More information about the samba-cvs
mailing list