From 34a681a5d75e700dd3e7b601b1f6b9004ad67abf Mon Sep 17 00:00:00 2001 From: Moe Jette <jette1@llnl.gov> Date: Tue, 25 May 2010 20:34:22 +0000 Subject: [PATCH] In various places change "Munge" to "MUNGE" --- doc/html/accounting.shtml | 28 ++++++++++++++-------------- doc/html/download.shtml | 14 +++++++------- doc/html/news.shtml | 2 +- doc/html/resource_limits.shtml | 2 +- 4 files changed, 23 insertions(+), 23 deletions(-) diff --git a/doc/html/accounting.shtml b/doc/html/accounting.shtml index cab0e72b2eb..3ef53bf9641 100644 --- a/doc/html/accounting.shtml +++ b/doc/html/accounting.shtml @@ -124,16 +124,16 @@ users should have consistent names and IDs.</p> <p>The best way to insure security of the data is by authenticating communications to the SlurmDBD and we recommend -<a href="http://munge.googlecode.com/">Munge</a> for that purpose. +<a href="http://munge.googlecode.com/">MUNGE</a> for that purpose. If you have one cluster managed by SLURM and execute the SlurmDBD -on that one cluster, the normal Munge configuration will suffice. -Otherwise Munge should then be installed on all nodes of all +on that one cluster, the normal MUNGE configuration will suffice. +Otherwise MUNGE should then be installed on all nodes of all SLURM managed clusters, plus the machine where SlurmDBD executes. -You then have a choice of either having a single Munge key for +You then have a choice of either having a single MUNGE key for all of these computers or maintaining a unique key for each of the clusters plus a second key for communications between the clusters for better security. -Munge enhancements are planned to support two keys within a single +MUNGE enhancements are planned to support two keys within a single configuration file, but presently two different daemons must be started with different configurations to support two different keys (create two key files and start the daemons with the @@ -145,11 +145,11 @@ respectively, more details are provided below).</p> <p?Whether you use any authentication module or not you will need to have a way for the SlurmDBD to get uid's for users and/or admin. If using -Munge, it is ideal for your users to have the same id on all your +MUNGE, it is ideal for your users to have the same id on all your clusters. If this is the case you should have a combination of every clusters /etc/passwd file on the database server to allow the DBD to resolve -names for authentication. If using Munge and a users name is not in -the passwd file the action will fail. If not using Munge, you should +names for authentication. If using MUNGE and a users name is not in +the passwd file the action will fail. If not using MUNGE, you should add anyone you want to be an administrator or operator to the passwd file. If they plan on running sacctmgr or any of the accounting tools they should have the same uid, or they will not authentic correctly. An @@ -266,9 +266,9 @@ time their limits per association.</li> <li><b>AccountingStorageHost</b>: The name or address of the host where SlurmDBD executes</li> -<li><b>AccountingStoragePass</b>: If using SlurmDBD with a second Munge -daemon, store the pathname of the named socket used by Munge to provide -enterprise-wide. Otherwise the default Munge daemon will be used.</li> +<li><b>AccountingStoragePass</b>: If using SlurmDBD with a second MUNGE +daemon, store the pathname of the named socket used by MUNGE to provide +enterprise-wide. Otherwise the default MUNGE daemon will be used.</li> <li><b>AccountingStoragePort</b>: The network port that SlurmDBD accepts communication on.</li> @@ -301,9 +301,9 @@ Some of the more important parameters include:</p> <ul> <li><b>AuthInfo</b>: -If using SlurmDBD with a second Munge daemon, store the pathname of -the named socket used by Munge to provide enterprise-wide. -Otherwise the default Munge daemon will be used.</li> +If using SlurmDBD with a second MUNGE daemon, store the pathname of +the named socket used by MUNGE to provide enterprise-wide. +Otherwise the default MUNGE daemon will be used.</li> <li><b>AuthType</b>: Define the authentication method for communications between SLURM diff --git a/doc/html/download.shtml b/doc/html/download.shtml index 9c094d4f1d3..b703f5f62a2 100644 --- a/doc/html/download.shtml +++ b/doc/html/download.shtml @@ -17,9 +17,9 @@ SLURM has also been packaged for a message.</li> <ul> <li><a href="http://www.theether.org/authd">authd</a></li> -<li><b>Munge</b> (recommended)<br> +<li><b>MUNGE</b> (recommended)<br> In order to compile the "auth/munge" authentication plugin for SLURM, -you will need to build and install Munge, available from +you will need to build and install MUNGE, available from <a href="http://munge.googlecode.com/">http://munge.googlecode.com/</a> and <a href="http://packages.debian.org/src:munge">Debian</a> and <a href="http://fedoraproject.org/">Fedora</a> and @@ -45,12 +45,12 @@ It's an open source, non-interactive, command line, scriptable tool intended for <li><b>Digital signatures</b> (Cypto plugin) are used to insure message are not altered.</li> <ul> -<li><b>Munge</b> (recommended)<br> -Munge can be used at an alternative to OpenSSL. -Munge is available under the Gnu General Public License. -See Munge download information above.</li> +<li><b>MUNGE</b> (recommended)<br> +MUNGE can be used at an alternative to OpenSSL. +MUNGE is available under the Gnu General Public License. +See MUNGE download information above.</li> <li><b>OpenSSL</b><br> -OpenSSL may be used as an alternative to Munge for generation of digital signatures. +OpenSSL may be used as an alternative to MUNGE for generation of digital signatures. Download it from <a href="http://www.openssl.org/">http://www.openssl.org/</a>.</li> </ul><br> diff --git a/doc/html/news.shtml b/doc/html/news.shtml index c23453623ac..8431fb44cab 100644 --- a/doc/html/news.shtml +++ b/doc/html/news.shtml @@ -22,7 +22,7 @@ database support across multiple clusters.</li> <li>Gang scheduler plugin added (time-slicing of parallel jobs without an external scheduler).</li> <li>Cryptography logic moved to a separate plugin with the -option of using OpenSSL (default) or Munge (GPL).</li> +option of using OpenSSL (default) or MUNGE (GPL).</li> <li>Improved scheduling of multiple job steps within a job's allocation.</li> <li>Support for job specification of node features with node counts.</li> <li><i>srun</i>'s --alloc, --attach, and --batch options removed (use diff --git a/doc/html/resource_limits.shtml b/doc/html/resource_limits.shtml index c7a2bf859ab..786433ce842 100644 --- a/doc/html/resource_limits.shtml +++ b/doc/html/resource_limits.shtml @@ -25,7 +25,7 @@ or <a href="http://www.postgresql.org/">PostgreSQL</a>. For security and performance reasons, the use of SlurmDBD (SLURM Database Daemon) as a front-end to the database is strongly recommended. -SlurmDBD uses a SLURM authentication plugin (e.g. Munge). +SlurmDBD uses a SLURM authentication plugin (e.g. MUNGE). SlurmDBD also uses an existing SLURM accounting storage plugin to maximize code reuse. SlurmDBD uses data caching and prioritization of pending requests -- GitLab