blkmapd: allow blocklayoutdriver module to load/unload

[nfs-utils.git] / README

diff --git a/README b/README
index 6cd79c7432dbdbf5c9e981f1e22cd02a035b6473..e55b2ddcb11ae2146f597faf937e2d40fab709a9 100644 (file)
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-This is version 1.0.1 of nfs-utils, the Linux NFS utility package.
+This is version 1.2.6 of nfs-utils, the Linux NFS utility package.
 
 
 0. PROJECT RESOURCES
@@ -15,6 +15,8 @@ libraries.  They are available from
    http://www.citi.umich.edu/projects/nfsv4/linux/libnfsidmap/
 Otherwise use --disable-nfsv4
 
+To use the nfsdcld tracking daemon, nfsv4 support must be enabled,
+and the libsqlite3 development libraries must be installed.
 
 1. COMPILING
 
@@ -48,7 +50,7 @@ Finally, build as usual as above.
 3. DAEMON STARTUP ORDER
 
 This nfs-utils packages does not provide any scripts for starting
-various daemons as mast distributions replace them with their own, so
+various daemons as most distributions replace them with their own, so
 any scripts we package would not get much testing.
 Instead, we explain the dependencies involved in startup so that
 scripts can be written to work correctly.
@@ -78,10 +80,12 @@ scripts can be written to work correctly.
        These supply services to nfsd and so should be started before
        rpc.nfsd.  Where they come between mounting the nfsd filesystem
        and starting the nfsd server is not important.
-       idmapd is only need for NFSv4 support.
+       idmapd is only needed for NFSv4 support.
+       svcgssd is only needed if exportfs NFS filesystem with crypto-
+       security (Kerberos).
 
    C/ exportfs -av ; rpc.mountd
-       If it important that exportfs be run before mountd so that
+       It is important that exportfs be run before mountd so that
        mountd is working from current information (in
        /var/lib/nfs/etab).
        It is also important that both of these are run before
@@ -104,12 +108,31 @@ scripts can be written to work correctly.
        the lock.
        rpc.statd is only needed for NFSv2 and NFSv3 support.
 
-   E/ rpc.nfsd
+   E/ nfsdcld
+       This daemon is only needed on kernels that support the nfsdcld
+       upcall, and only if the legacy client ID tracking isn't used. It
+       is also not needed if the server does not support NFSv4.
+
+       To determine whether you need this or not, do the following:
+
+           # cat /proc/fs/nfsd/versions
+
+       That should yield a list of NFS versions that this kernel supports,
+       if "4" or later is not in that list, or they are prefixed with a "-"
+       then you don't need to run this daemon. Next:
+
+           # cat /proc/fs/nfsd/nfsv4recoverydir
+
+       If that file is not present, or the directory that the above command
+       outputs is not present, then this daemon is required in order to
+       support lock recovery by the clients when the server reboots.
+
+   F/ rpc.nfsd
        Starting nfsd will automatically start lockd.  The nfs server
        will now be fully active and respond to any requests from
        clients.
        
-   F/ sm-notify
+   G/ sm-notify
        This will notify any client which might have locks from before
        a reboot to try to reclaim their locks.  This should start
        immediately after rpc.nfsd is started so that clients have a
@@ -126,7 +149,9 @@ scripts can be written to work correctly.
       This is appropriate for '/', '/usr', and '/var'.
 
    B/ gssd ; idmapd
-      (I need some guidance here).
+      idmapd should be started before mounting any NFSv4 filesystems.
+      gssd should be started before mounting any NFS filesystems
+      securely (with Kerberos).
 
    C/ statd should be run before any NFSv2 or NFSv3 filesystem is
       mounted with remote locking (i.e. without -o nolock).
@@ -146,7 +171,11 @@ scripts can be written to work correctly.
       Each should try to start when they need it.
 
    C/ idmapd
-      (I need some guidance here).
+
+      Both the server and client need idmapd to be running.  If idmapd
+      is started (for the client) before starting nfsd the 'nfsd'
+      filesystem is mounted, then idmapd should be sent a HUP signal
+      afterwards to signal that the server channels should be opened.
 
    
       
@@ -154,4 +183,4 @@ scripts can be written to work correctly.
 Share And Enjoy!
 
     -- the nfs-utils developers
-       <nfs@lists.sourceforge.net>
+       <linux-nfs@vger.kernel.org>