Change slurm-dev references to slurm-users.

Mailing list has been renamed. Update links.

Drop Gmane link, as they apparently stopped archiving things
over a year ago, and the relay point has now been dropped from
the slurm-users list.

Drop mentions of emailing slurm-dev from the FAQ. The mailing
list auto-discards anything from non-subscribors.

doc/html/faq.shtml

@@ -47,7 +47,7 @@
 <li><a href="#mem_limit">Why are jobs not getting the appropriate
   memory limit?</a></li>
 <li><a href="#mailing_list">Is an archive available of messages posted to
-  the <i>slurm-dev</i> mailing list?</a></li>
+  the <i>slurm-users</i> mailing list?</a></li>
 <li><a href="#job_size">Can I change my job's size after it has started
   running?</a></li>
 <li><a href="#mpi_symbols">Why is my MPIHCH2 or MVAPICH2 job not running with
@@ -707,9 +707,9 @@ Use the same solution for the AS (Address Space), RSS (Resident Set Size),
 or other limits as needed.</p>
 
 <p><a name="mailing_list"><b>23. Is an archive available of messages posted to
-the <i>slurm-dev</i> mailing list?</b></a><br>
-Yes, it is at <a href="http://groups.google.com/group/slurm-devel">
-http://groups.google.com/group/slurm-devel</a></p>
+the <i>slurm-users</i> mailing list?</b></a><br>
+Yes, it is at <a href="http://groups.google.com/group/slurm-users">
+http://groups.google.com/group/slurm-users</a></p>
 
 <p><a name="job_size"><b>24. Can I change my job's size after it has started
 running?</b></a><br>

doc/html/mail.shtml

 <!--#include virtual="header.txt"-->
 
 <h1>Mailing Lists</h1>
-<p>We maintain two Slurm mailing lists:</p>
+<p>SchedMD maintains two Slurm mailing lists:</p>
 <ul>
 <li><b>slurm-announce@schedmd.com</b> is designated for communications about
-Slurm releases. The ability to post to this list is restricted to a few Slurm
-developers [low traffic].</li>
-<li><b>slurm-dev@schedmd.com</b> is designated for communications to Slurm
-developers and is typically used by Slurm users or system administrators.
-Any person subscribed to this mailing list may post to it.
-[high traffic at times].</li>
+Slurm releases. Only SchedMD may post to this list. Low traffic.</li>
+<li><b>slurm-users@schedmd.com</b> (formerly slurm-dev@schedmd.com) is for
+discussion by the Slurm community, and is typically used by Slurm system
+administrators for discussion and community-provided support. (Please see the
+<a href="https://www.schedmd.com/support.php">SchedMD support page</a>
+page for commercial support options.)
+Any person subscribed to this mailing list may post to it. High traffic.</li>
 </ul>
 
-<p>The <i>slurm-dev@schedmd.com</i> mailing list is a good mechanism for the
-user community to share information.</p>
+<p>You can subscribe to either list, change your subscription options, or
+unsubscribe through the
+<a href="https://lists.schedmd.com/cgi-bin/mailman/">Mailman interface here</a>.</p>
 
-<p>You can join either list
-  by <a href="https://lists.schedmd.com/cgi-bin/dada/mail.cgi/list">subscribing
-  here</a>.
+<p>An archive of the <b>slurm-users</b> list is online:<br>
+<a href="http://groups.google.com/group/slurm-users">http://groups.google.com/group/slurm-users</a></p>
 
-<p>
-You can unsubscribe by logging
-into <a href="https://lists.schedmd.com/cgi-bin/dada/mail.cgi/profile_login/">your
-    mailing list profile</a>, or email <a href="mailto:unsubscribe@schedmd.com?Subject=Unsubscribe">unsubscribe@schedmd.com</a>.
-</p>
-
-<p>The archive of the <b>slurm-dev</b> list is online:<br>
-<a href="http://dir.gmane.org/gmane.comp.distributed.slurm.devel">http://dir.gmane.org/gmane.comp.distributed.slurm.devel</a><br>
-and<br>
-<a href="http://groups.google.com/group/slurm-devel">http://groups.google.com/group/slurm-devel</a></p>
-
-<p style="text-align:center;">Last modified 29 April 2015</p>
+<p style="text-align:center;">Last modified 5 November 2017</p>
 
 <!--#include virtual="footer.txt"-->

doc/html/troubleshoot.shtml

@@ -52,9 +52,7 @@ daemon by executing "<i>ps -el | grep slurmctld</i>".</li>
 <li>If slurmctld is not running, restart it (typically as user root
 using the command "<i>/etc/init.d/slurm start</i>").
 You should check the log file (<i>SlurmctldLog</i> in the
-<i>slurm.conf</i> file) for an indication of why it failed.
-If it keeps failing, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
+<i>slurm.conf</i> file) for an indication of why it failed.</li>
 
 <li>If slurmctld is running but not responding (a very rare situation),
 then kill and restart it (typically as user root using the commands
@@ -63,9 +61,7 @@ then kill and restart it (typically as user root using the commands
 <li>If it hangs again, increase the verbosity of debug messages
 (increase <i>SlurmctldDebug</i> in the <i>slurm.conf</i> file)
 and restart.
-Again check the log file for an indication of why it failed.
-At this point, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
+Again check the log file for an indication of why it failed.</li>
 
 <li>If it continues to fail without an indication as to the failure
 mode, restart without preserving state (typically as user root
@@ -161,9 +157,7 @@ You can get the status of the running slurmd daemon by
 executing the command "<i>scontrol show slurmd</i>" on
 the node of interest.
 Check the value of "Last slurmctld msg time" to determine
-if the slurmctld is able to communicate with the slurmd.
-If it keeps failing, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
+if the slurmctld is able to communicate with the slurmd.</li>
 
 <li>If slurmd is running but not responding (a very rare situation),
 then kill and restart it (typically as user root using the commands
@@ -175,9 +169,7 @@ then kill and restart it (typically as user root using the commands
 <li>If still not responding, increase the verbosity of debug messages
 (increase <i>SlurmdDebug</i> in the <i>slurm.conf</i> file)
 and restart.
-Again check the log file for an indication of why it failed.
-At this point, you should contact the slurm team for help at
-<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
+Again check the log file for an indication of why it failed.</li>
 
 <li>If still not responding without an indication as to the failure
 mode, restart without preserving state (typically as user root