From c55b2109c75d4f0df39bff832a309b6e66912406 Mon Sep 17 00:00:00 2001
From: Morris Jette <jette@schedmd.com>
Date: Wed, 8 Oct 2014 14:49:18 -0700
Subject: [PATCH] Expand documentation for chosloc config parameter

---
 doc/man/man5/slurm.conf.5 | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/doc/man/man5/slurm.conf.5 b/doc/man/man5/slurm.conf.5
index 397731587b8..053fc57e629 100644
--- a/doc/man/man5/slurm.conf.5
+++ b/doc/man/man5/slurm.conf.5
@@ -374,7 +374,15 @@ for use with IBM POE (Parallel Operating Environment) only
 
 .TP
 \fBChosLoc\fR
-The fully qualified pathname of the chos command if the Chroot OS tool is used
+If configured, then any processes invoked on the user behalf (namely the
+SPANK prolog/epilog scripts and the slurmstepd processes, which in turn spawn
+the user batch script and applications) are not directly executed by the slurmd
+daemon, but instead the \fBChosLoc\fR program is executed.
+That program's argument are the program and arguments that would otherwise be
+invoked directly by the slurmd daemon.
+The intent of this feature is to be able to run a user application in some
+sort of container.
+This option specified the fully qualified pathname of the chos command
 (see https://github.com/scanon/chos for details).
 
 .TP
-- 
GitLab