Skip to content
Snippets Groups Projects
Commit b93c80eb authored by Morris Jette's avatar Morris Jette
Browse files

Change mailing list addresses from llnl.gov to schedmd.com

parent 87af27d2
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/html/accounting.shtml
+ 3
− 2
View file @ b93c80eb
...@@ -193,7 +193,8 @@ a configuration. ...@@ -193,7 +193,8 @@ a configuration.
supported for job and step accounting only.</b> The infrastructure for supported for job and step accounting only.</b> The infrastructure for
PostgresSQL for use with associations is not yet supported, meaning PostgresSQL for use with associations is not yet supported, meaning
sacctmgr will not work correctly. If interested in adding this sacctmgr will not work correctly. If interested in adding this
capability for PostgresSQL, please contact us at slurm-dev@lists.llnl.gov. capability for PostgresSQL, please contact us at
<a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.
<p>To enable this database support <p>To enable this database support
one only needs to have the development package for the database they one only needs to have the development package for the database they
...@@ -777,7 +778,7 @@ as deleted. ...@@ -777,7 +778,7 @@ as deleted.
If an entity has existed for less than 1 day, the entity will be removed If an entity has existed for less than 1 day, the entity will be removed
completely. This is meant to clean up after typographic errors.</p> completely. This is meant to clean up after typographic errors.</p>
<p style="text-align: center;">Last modified 10 June 2010</p> <p style="text-align: center;">Last modified 3 February 2012</p>
<!--#include virtual="footer.txt"--> <!--#include virtual="footer.txt"-->
doc/html/cons_res.shtml
+ 2
− 2
View file @ b93c80eb
...@@ -152,7 +152,7 @@ resource plug-in and plan to make enhancement the plug-in as we get ...@@ -152,7 +152,7 @@ resource plug-in and plan to make enhancement the plug-in as we get
time as well as request from users to help us prioritize the features. time as well as request from users to help us prioritize the features.
Please send comments and requests about the consumable resources to Please send comments and requests about the consumable resources to
<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>. <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.
<ol start=1 type=1> <ol start=1 type=1>
<li><b>Issue with --max_nodes, --max_sockets_per_node, --max_cores_per_socket and --max_threads_per_core</b></li> <li><b>Issue with --max_nodes, --max_sockets_per_node, --max_cores_per_socket and --max_threads_per_core</b></li>
...@@ -446,6 +446,6 @@ one mpi process per node.</p> ...@@ -446,6 +446,6 @@ one mpi process per node.</p>
<p class="footer"><a href="#top">top</a></p> <p class="footer"><a href="#top">top</a></p>
<p style="text-align:center;">Last modified 8 July 2008</p> <p style="text-align:center;">Last modified 3 February 2012</p>
<!--#include virtual="footer.txt"--> <!--#include virtual="footer.txt"-->
doc/html/help.shtml
+ 2
− 2
View file @ b93c80eb
...@@ -13,13 +13,13 @@ helps you resolve the problem.</li> ...@@ -13,13 +13,13 @@ helps you resolve the problem.</li>
their support staff.</li> their support staff.</li>
<li>Send a detailed description of the problem, the output from the command <li>Send a detailed description of the problem, the output from the command
"scontrol show config", logs, back traces from any core files, etc. to "scontrol show config", logs, back traces from any core files, etc. to
<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li> <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
</ol> </ol>
<h1>Commercial Support</h1> <h1>Commercial Support</h1>
<p>Several companies provide commercial support for SLURM including <p>Several companies provide commercial support for SLURM including
<a href="http://www.schedmd.com">SchedMD</a>.</p> <a href="http://www.schedmd.com">SchedMD</a>.</p>
<p style="text-align:center;">Last modified 30 June 2011</p> <p style="text-align:center;">Last modified 3 February 2012</p>
<!--#include virtual="footer.txt"--> <!--#include virtual="footer.txt"-->
doc/html/news.shtml
+ 2
− 2
View file @ b93c80eb
...@@ -85,7 +85,7 @@ of "AMD").</li> ...@@ -85,7 +85,7 @@ of "AMD").</li>
<h2><a name="25">Major Updates in SLURM Version 2.5 and beyond</a></h2> <h2><a name="25">Major Updates in SLURM Version 2.5 and beyond</a></h2>
<p> Detailed plans for release dates and contents of additional SLURM releases <p> Detailed plans for release dates and contents of additional SLURM releases
have not been finalized. Anyone desiring to perform SLURM development should have not been finalized. Anyone desiring to perform SLURM development should
notify <a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a> notify <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>
to coordinate activities. Future development plans includes: to coordinate activities. Future development plans includes:
<ul> <ul>
<li>Faster and more powerful job step management support (e.g. step <li>Faster and more powerful job step management support (e.g. step
...@@ -124,6 +124,6 @@ trojan library, then that library will be used by the SLURM daemon with ...@@ -124,6 +124,6 @@ trojan library, then that library will be used by the SLURM daemon with
unpredictable results. This was fixed in SLURM version 2.1.14.</li> unpredictable results. This was fixed in SLURM version 2.1.14.</li>
</ul> </ul>
<p style="text-align:center;">Last modified 6 January 2012</p> <p style="text-align:center;">Last modified 3 February 2012</p>
<!--#include virtual="footer.txt"--> <!--#include virtual="footer.txt"-->
doc/html/slurm_ug_cfp.shtml
+ 1
− 1
View file @ b93c80eb
...@@ -22,7 +22,7 @@ SLURM</a>, a highly scalable Resource Manager and Job Scheduler</li> ...@@ -22,7 +22,7 @@ SLURM</a>, a highly scalable Resource Manager and Job Scheduler</li>
<p>Everyone who wants to present their own usage, developments, site report, <p>Everyone who wants to present their own usage, developments, site report,
or tutorial about SLURM is invited to send a short abstract including or tutorial about SLURM is invited to send a short abstract including
the presentation's expected duration to the presentation's expected duration to
<a href="mailto:slurm_user_group@lists.llnl.gov">slurm_user_group@lists.llnl.gov</a>.</p> <a href="mailto:slurm_user_group@schedmd.com">slurm_user_group@schedmd.com</a>.</p>
<p>IMPORTANT DATES:<br> <p>IMPORTANT DATES:<br>
April 30, 2011: Submission of abstracts<br> April 30, 2011: Submission of abstracts<br>
......
doc/html/slurm_ug_registration.shtml
+ 1
− 1
View file @ b93c80eb
...@@ -41,7 +41,7 @@ ...@@ -41,7 +41,7 @@
You should receive a confirmation of this initial stage within in a few days and You should receive a confirmation of this initial stage within in a few days and
final confirmation by <b>August 26, 2011</b>.</p> final confirmation by <b>August 26, 2011</b>.</p>
<FORM METHOD=POST ENCTYPE="text/plain" ACTION="mailto:slurm_user_group@lists.llnl.gov?subject=SLURM User Group Registration"> <FORM METHOD=POST ENCTYPE="text/plain" ACTION="mailto:slurm_user_group@schedmd.com?subject=SLURM User Group Registration">
<PRE> <PRE>
<table width="100%" border=0 cellspacing=0 cellpadding=0> <table width="100%" border=0 cellspacing=0 cellpadding=0>
<tr> <tr>
......
doc/html/troubleshoot.shtml
+ 5
− 5
View file @ b93c80eb
...@@ -54,7 +54,7 @@ using the command "<i>/etc/init.d/slurm start</i>"). ...@@ -54,7 +54,7 @@ using the command "<i>/etc/init.d/slurm start</i>").
You should check the log file (<i>SlurmctldLog</i> in the You should check the log file (<i>SlurmctldLog</i> in the
<i>slurm.conf</i> file) for an indication of why it failed. <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 If it keeps failing, you should contact the slurm team for help at
<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li> <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
<li>If slurmctld is running but not responding (a very rare situation), <li>If slurmctld is running but not responding (a very rare situation),
then kill and restart it (typically as user root using the commands then kill and restart it (typically as user root using the commands
...@@ -65,7 +65,7 @@ then kill and restart it (typically as user root using the commands ...@@ -65,7 +65,7 @@ then kill and restart it (typically as user root using the commands
and restart. and restart.
Again check the log file for an indication of why it failed. Again check the log file for an indication of why it failed.
At this point, you should contact the slurm team for help at At this point, you should contact the slurm team for help at
<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li> <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
<li>If it continues to fail without an indication as to the failure <li>If it continues to fail without an indication as to the failure
mode, restart without preserving state (typically as user root mode, restart without preserving state (typically as user root
...@@ -165,7 +165,7 @@ the node of interest. ...@@ -165,7 +165,7 @@ the node of interest.
Check the value of "Last slurmctld msg time" to determine Check the value of "Last slurmctld msg time" to determine
if the slurmctld is able to communicate with the slurmd. if the slurmctld is able to communicate with the slurmd.
If it keeps failing, you should contact the slurm team for help at If it keeps failing, you should contact the slurm team for help at
<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li> <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
<li>If slurmd is running but not responding (a very rare situation), <li>If slurmd is running but not responding (a very rare situation),
then kill and restart it (typically as user root using the commands then kill and restart it (typically as user root using the commands
...@@ -179,7 +179,7 @@ then kill and restart it (typically as user root using the commands ...@@ -179,7 +179,7 @@ then kill and restart it (typically as user root using the commands
and restart. and restart.
Again check the log file for an indication of why it failed. Again check the log file for an indication of why it failed.
At this point, you should contact the slurm team for help at At this point, you should contact the slurm team for help at
<a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</li> <a href="mailto:slurm-dev@schedmd.com">slurm-dev@schedmd.com</a>.</li>
<li>If still not responding without an indication as to the failure <li>If still not responding without an indication as to the failure
mode, restart without preserving state (typically as user root mode, restart without preserving state (typically as user root
...@@ -296,6 +296,6 @@ partition 000. ...@@ -296,6 +296,6 @@ partition 000.
</ol> </ol>
<p class="footer"><a href="#top">top</a></p> <p class="footer"><a href="#top">top</a></p>
<p style="text-align:center;">Last modified 7 July 2007</p> <p style="text-align:center;">Last modified 3 February 2012</p>
<!--#include virtual="footer.txt"--> <!--#include virtual="footer.txt"-->
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
Nutzungsbedingungen | Datenschutzerklärung | Barrierefreiheitserklärung