Index: trunk/docs/HOWTO-client+server-troubleshooting.html
===================================================================
--- trunk/docs/HOWTO-client+server-troubleshooting.html	(revision 591)
+++ trunk/docs/HOWTO-client+server-troubleshooting.html	(revision 1)
@@ -30,5 +30,4 @@
 div.warnblock {
 	background: #b6c5f2; color: #000;
-	background: #ffffcc; color: #000;
 	margin: 1em; padding: 0 1em 0 1em;
 	border-width: 1px;
@@ -132,29 +131,4 @@
 <br>
 <hr>
-<div class="warnblock">
-<ul>
-  <li>Almost all problems can only be diagnosed correctly by checking the 
-      <b>server logs</b>.</li>
-  <li>
-    If the server does not write logs, <b>fix this first</b>. For debugging, 
-    stop the server, then run it in the foreground with 
-    <tt>yule -p info --foreground</tt>
-    <ul>
-      <li>
-	By default, the server logs to the file 
-	<tt>/var/log/yule/yule_log</tt>, and since the server drops 
-	root privileges on startup, the directory <tt>/var/log/yule</tt>
-	must be writable for the nonprivileged user the server runs 
-	as (the first existing out of: yule, daemon, nobody).
-      </li>
-      <li>
-	Logging to the logfile must be enabled in the
-	<tt>/etc/yulerc</tt> config file (e.g. LogSeverity=mark, or 
-	LogSeverity=info for enhanced verbosity).
-      </li>
-    </ul>
-  </li>
-</ul>
-</div>
 <p>
 This document aims to explain how to diagnose and fix common problems that
@@ -273,25 +247,13 @@
      <p>
      <p>
-     This does not work for a number of people because
-     <ol>
-       <li>
-	 the
-	 <tt>/etc/hosts</tt> file on the client machine has errors 
-	 (yes, there are plenty machines with a completely 
-	 messed up <tt>/etc/hosts</tt> file),
-       </li>
-       <li>
-	 the
-	 server cannot resolve the client address because the local DNS is
-	 misconfigured, or 
-       </li>
-       <li> 
-	 the client machine has multiple network interfaces, and
-	 the interface used is not the one the client name resolves to.
-       </li>
-     </ol>
-     </p>
-
-     <p>
+     This does not work for a number of people because (1) the
+     <tt>/etc/hosts</tt> file on the client machine has errors 
+     (yes, there are plenty machines with a completely 
+     messed up <tt>/etc/hosts</tt> file), (2) the
+     server cannot resolve the client address because the local DNS is
+     f***ed up, or (3) the client machine has multiple network interfaces, and
+     the interface used is not the one the client name resolves to.
+     </p>
+       <p>
        If the client uses the wrong interface on a multi-interface machine, 
        there is a config file option 
@@ -299,30 +261,29 @@
        that allows to choose the interface the client will use for
        outgoing connections.
-     </p>
-     <p>
+       </p>
+       <p>
        If you want to download the config file from the server, you
-       should instead use the corresponding command line option
+       should instead use the corresponding command line
        <tt>--bind-address=</tt><i>IP address</i>
        to select the interface.
-     </p>
-
-     <p>
-       If you encounter problems, you may (1) fix your 
-       <tt>/etc/hosts</tt> file(s), (2) fix your local DNS, or
-       (3) switch to the second method.
-     </p>
-     <p>
-       Error messages related to name resolving/cross-checking can be 
-       suppressed by setting a 
-       very low severity (lower than the logging threshold), e.g.
-     </p>
-     <p>
-       <tt>SeverityLookup=</tt><i>debug</i>
-     </p>
-     <p>
-       in the <i>Misc</i> section of the server configuration,
-       if you prefer running <i>unsafe</i> at any speed 
-       instead of fixing the problem (you have been warned). Doing so will
-       allow an attacker to pose as the client.
+       </p>
+
+     <p>
+     If you encounter problems, you may (1) fix your 
+     <tt>/etc/hosts</tt> file(s), (2) fix your local DNS, or
+     (3) switch to the second method.
+     </p>
+     <p>
+     Errors in name resolving/cross-checking can be avoided by setting a 
+     very low severity (lower than the logging threshold), e.g.
+     </p>
+     <p>
+     <tt>SeverityLookup=</tt><i>debug</i>
+     </p>
+     <p>
+     in the <i>Misc</i> section of the server configuration,
+     if you prefer running <i>unsafe</i> at any speed 
+     instead of fixing the problem (you have been warned). Doing so will
+     allow an attacker to pose as the client.
      </p>
   </li>
@@ -353,6 +314,5 @@
 <p>
 The client does <i>not</i> tell the server the path to the requested
-file - it just tells the <em>type</em> of the file, i.e. 
-either a configuration file or a database file. It is entirely the
+file - it just requests a config or a database file. It's entirely the
 responsibility of the server to locate the correct file and send it.
 </p>
@@ -385,15 +345,4 @@
 To fix: put the file in the correct location, make sure the permissions
 are ok.
-<ul>
-  <li>
-    Note that <em>the server drops root privileges at startup</em> and
-    runs as an unprivileged user (the first existing out of: 
-    yule, daemon, nobody).
-  </li>
-  <li>
-    Also remember that to access a file, at least execute permission is required
-    <em>for every directory in the path</em>.
-  </li>
-</ul>
 </p>