From 50a19f776209efd3d52c69ee7b0e498a8ba5ff9b Mon Sep 17 00:00:00 2001
From: Casey Bodley <cbodley@citi.umich.edu>
Date: Fri, 23 Dec 2011 11:42:27 -0500
Subject: [PATCH] readme: note about nfsd_debug.exe in binary distribution

Signed-off-by: Casey Bodley <cbodley@citi.umich.edu>
---
 README.html | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.html b/README.html
index 87cd865..2eb7323 100644
--- a/README.html
+++ b/README.html
@@ -102,6 +102,9 @@
     <li>Uncomment the <code>ldap_hostname</code> and <code>ldap_base</code> lines, and configure as appropriate to match your ldap server configuration (we'll add suggestions later).</li>
 </ol>
 <h2>4. <a name="startup">Starting the Client</a></h2>
+<ul>
+    <li>If you've installed the binary distribution, you'll find two versions of the nfs client daemon: <strong>nfsd.exe</strong> and <strong>nfsd_debug.exe</strong>. <strong>nfsd.exe</strong> is built to run as a service, and does not provide easy access to debug output. We strongly recommend trying <strong>nfsd_debug.exe</strong> first (using the Instructions below) to verify that you can start the daemon and mount/unmount an nfs share. You can then close <strong>nfsd_debug.exe</strong> and start running <strong>nfsd.exe</strong> as a service with:<br /><code>&gt nfsd.exe -install</code>.</li>
+</ul>
 <h3>Instructions</h3>
 <ol>
     <li>From a Windows command prompt, run <strong>nfsd.exe</strong> to start the nfs client daemon. Leave this running in the background until all mapped drives are unmounted.