Update upgrade documentation

doc/html/quickstart_admin.shtml

@@ -691,7 +691,13 @@ but may also include very minor enhancements.</p>
 release number as the Slurmctld daemons.
 In other words, when changing the version to a higher release number (e.g
 from 2.4 to 2.5) <b>always upgrade the SlurmDBD daemon first</b>.
-The slurmctld daemon must also be upgraded before or at the same time as
+Database table changes may be required for the upgrade, for example
+adding new fields to existing tables.
+If the database contains a large number of entries, <b>the SlurmDBD daemon
+may require tens of minutes to update the database and be unresponsive
+during this time interval</b>.</p>
+
+<p>The slurmctld daemon must also be upgraded before or at the same time as
 the slurmd daemons on the compute nodes.
 Generally upgrading Slurm on all of the login and compute nodes is recommended,
 although rolling upgrades are also possible (i.e. upgrading the head node(s)
@@ -718,7 +724,12 @@ versions (e.g. 2.5.0-pre1 to 2.5.0-pre2).
 We'll try to note these cases in the NEWS file.
 Contents of major releases are also described in the RELEASE_NOTES file.</p>
 
-<p>Be mindful of your configured SlurmdTimeout and SlurmctldTimeout values.
+<p>The libslurm.so version is increasaed every major release.
+So things like MPI libraries with Slurm integration should be recompiled.
+Sometimes it works to just symlink the old so name(s) to the new one, but this
+has no guarantee of working.</p>
+
+<p><b>Be mindful of your configured SlurmdTimeout and SlurmctldTimeout values</b>.
 If your Slurm daemon down time associated with an upgrade take longer than
 the timeout value, nodes may be marked DOWN and their jobs killed.
 You can either increase timeout values during an upgrade or insure that your
@@ -765,6 +776,6 @@ options such as mysql and gui tools via a configuration menu.</p>
 
 </pre> <p class="footer"><a href="#top">top</a></p>
 
-<p style="text-align:center;">Last modified 29 May 2014</p>
+<p style="text-align:center;">Last modified 11 June 2014</p>
 
 <!--#include virtual="footer.txt"-->