*** empty log message ***

SVN revision: 1151

doc/adminguide.html

@@ -236,7 +236,7 @@ option in <code>elogd.cfg</code> to <code><b>port=80</code></B> and restarting e
 <p>with :
 <ul>
 <li><code>-p &lt;port&gt;</code>&nbsp; TCP port number to use for the http server (if other than 80)
-<li><code>-h &lt;hostname or IP address&gt;</code> in the case of a "multihomed" server, host name or IP 
+<li><code>-h &lt;hostname or IP address&gt;</code> in the case of a "multihomed" server, host name or IP
   address of the interface ELOG should run on
 <LI><code>-C &lt;url&gt;</code>&nbsp; clone remote elogd configuration&nbsp;
 <LI><code>-m</code>&nbsp; synchronize logbook(s) with remote server
@@ -300,7 +300,10 @@ accordingly and a certificate has to be generated. See some
 on how to create a certificate, and see <i>Running elogd under Apache</i>
 before on this page on how to run elogd under Apache. Once configured
 correctly, elogd can be accessed via <i>http://your.host</i> and via
-<i>https://your.host</i> simultaneously.<p>
+<i>https://your.host</i> simultaneously.<br><br>
+
+For detailed step-by-step instructions please read the
+<a href="http://midas.psi.ch/elogs/contributions/11">contributions section<a>.
 
 <h3><i>Using ssh</i>:</h3>
 
@@ -317,6 +320,10 @@ access <b> <code>http://localhost:1234</code></b> from your browser and reach
 
 <h3><i>Using stunnel</i>:</h3>
 
+<i><b>Note: It was reported that the below instructions are outdated. However
+I will leave them for a while as a working basis for someone who volunteers
+to update them.</i></b>.<p>
+
 To use <code><b>elogd</b></code> togethwer with
 <a href="http://www.stunnel.or/g">stunnel</a>, following steps are necessary:
 
@@ -353,10 +360,6 @@ details.
 
 This reveals any potential error.<p></p></LI>
 </OL>
-
-<i>Please note that the stunnel syntax might be outdated by now. If anybody
-can figure out a more recent description I'm happy to include it here.</i><p></p>
-
 <p>
 
 <hr><a name="tech">