Skip to content
Snippets Groups Projects
Commit af4fc08e authored by Moe Jette's avatar Moe Jette
Browse files

Update document per feedback from Edwin Varella.

parent 8829c3f1
No related branches found
No related tags found
No related merge requests found
......@@ -9,7 +9,7 @@
<meta http-equiv="keywords" content="Simple Linux Utility for Resource Management, SLURM, resource management,
Linux clusters, high-performance computing, Livermore Computing">
<meta name="LLNLRandR" content="UCRL-WEB-209488">
<meta name="LLNLRandRdate" content="18 May 2005">
<meta name="LLNLRandRdate" content="19 May 2005">
<meta name="distribution" content="global">
<meta name="description" content="Simple Linux Utility for Resource Management">
<meta name="copyright"
......@@ -237,7 +237,9 @@ environment.
<p>The SLURM configuration file includes a wide variety of parameters.
This configuration file must be available on each node of the cluster. A full
description of the parameters is included in the slurm.conf man page. Rather than
duplicate that information, a sample configuration file is shown below. Any text
duplicate that information, a minimal sample configuration file is shown below.
Your slurm.conf file should define at least the configuration parameters defined
in this sample and likely additional ones. Any text
following a &quot;#&quot; is considered a comment. The keywords in the file are
not case sensitive, although the argument typically is (e.g., &quot;SlurmUser=slurm&quot;
might be specified as &quot;slurmuser=slurm&quot;). The control machine, like
......@@ -488,7 +490,7 @@ in the NEWS file.
<td colspan="3"><hr> <p>For information about this page, contact <a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</p>
<p><a href="http://www.llnl.gov/"><img align=middle src="lll.gif" width="32" height="32" border="0"></a></p>
<p class="footer">UCRL-WEB-209488<br>
Last modified 18 May 2005</p></td>
Last modified 19 May 2005</p></td>
</tr>
</table>
</td>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment