From 1c48b5a62f73234ed26bb20f0ab345ab61cda0ab Mon Sep 17 00:00:00 2001
From: Stephen Gallagher <sgallagh@redhat.com>
Date: Thu, 18 Feb 2010 07:49:04 -0500
Subject: Rename server/ directory to src/

Also update BUILD.txt
---
 server/man/include/failover.xml   | 42 ---------------------------------------
 server/man/include/param_help.xml | 10 ----------
 server/man/include/upstream.xml   |  4 ----
 3 files changed, 56 deletions(-)
 delete mode 100644 server/man/include/failover.xml
 delete mode 100644 server/man/include/param_help.xml
 delete mode 100644 server/man/include/upstream.xml

(limited to 'server/man/include')

diff --git a/server/man/include/failover.xml b/server/man/include/failover.xml
deleted file mode 100644
index efe3ee42..00000000
--- a/server/man/include/failover.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-<refsect1 id='failover'>
-    <title>FAILOVER</title>
-    <para>
-        The failover feature allows back ends to automatically switch to
-        a different server if the primary server fails.
-    </para>
-    <refsect2 id='failover_syntax'>
-        <title>Failover Syntax</title>
-        <para>
-            The list of servers is given as a comma-separated list; any
-            number of spaces is allowed around the comma. The servers are
-            listed in order of preference. The list can contain any number
-            of servers.
-        </para>
-    </refsect2>
-    <refsect2 id='failover_mechanism'>
-        <title>The Failover Mechanism</title>
-        <para>
-            The failover mechanism distinguishes between a machine and a
-            service. The back end first tries to resolve the hostname of a
-            given machine; if this resolution attempt fails, the machine is
-            considered offline. No further attempts are made to connect
-            to this machine for any other service. If the resolution
-            attempt succeeds, the back end tries to connect to a service
-            on this machine. If the service connection attempt fails,
-            then only this particular service is considered offline and
-            the back end automatically switches over to the next service.
-            The machine is still considered online and might still be tried
-            for another service.
-        </para>
-        <para>
-            Further connection attempts are made to machines or services
-            marked as offline after a specified period of time; this is
-            currently hard coded to 30 seconds.
-        </para>
-        <para>
-            If there are no more machines to try, the back end as a whole
-            switches to offline mode, and then attempts to reconnect
-            every 30 seconds.
-        </para>
-    </refsect2>
-</refsect1>
diff --git a/server/man/include/param_help.xml b/server/man/include/param_help.xml
deleted file mode 100644
index a2478bf2..00000000
--- a/server/man/include/param_help.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<varlistentry>
-    <term>
-        <option>-h</option>,<option>--help</option>
-    </term>
-    <listitem>
-        <para>
-            Display help message and exit.
-        </para>
-    </listitem>
-</varlistentry>
diff --git a/server/man/include/upstream.xml b/server/man/include/upstream.xml
deleted file mode 100644
index b6f633cc..00000000
--- a/server/man/include/upstream.xml
+++ /dev/null
@@ -1,4 +0,0 @@
-<refentryinfo>
-    <productname>SSSD</productname>
-    <orgname>The SSSD upstream - http://fedorahosted.org/sssd</orgname>
-</refentryinfo>
-- 
cgit