Fix example ipf_configure to use correct lmod_cache_file option

access-ci-org · Jul 5, 2024 · 6aca579 · 6aca579
1 parent fb1d9ee
commit 6aca579
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/docs/Quickstart.md b/docs/Quickstart.md
@@ -242,7 +242,7 @@ An invocation of ipf_configure on a resource that has installed
 IPF using RPM and wants to publish software information might look like:
 
 
-/usr/bin/ipf_configure --rpm --resource_name <RESOURCE_NAME> --workflows=extmodules --publish --amqp_certificate /etc/grid-security/cert_for_ipf.pem --amqp_certificate_key /etc/grid-security/key_for_ipf.pem  --modulepath /path/to/modules --mod_cache_file /path/to/lmodcache.lua
+/usr/bin/ipf_configure --rpm --resource_name <RESOURCE_NAME> --workflows=extmodules --publish --amqp_certificate /etc/grid-security/cert_for_ipf.pem --amqp_certificate_key /etc/grid-security/key_for_ipf.pem  --modulepath /path/to/modules --lmod_cache_file /path/to/lmodcache.lua
 
 
 These options mean:

diff --git a/ipf/step.py b/ipf/step.py
@@ -29,6 +29,8 @@
 class Step(multiprocessing.Process):
 
     def __init__(self):
+        # On MacOS, might need to force multiprocessing to use fork
+        # multiprocessing.set_start_method('fork',force=True)
         multiprocessing.Process.__init__(self)
 
         self.id = None        # a unique id for the step in a workflow