Page History
...
Multiple options were discussed. Solution #4 was eventually chosen. (October 2018)
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
Problem: procmgr needs location of conda.sh before activating conda env (including remote hosts)
Solution #1: hardcode the path in the procmgr code
Pro: expedient!
Con: maintenance nightmare -- path cannot be modified without new procmgr release
Solution #2: run 'conda info --base' locally
Pro: avoids hardcoding of path
Con: may require conda base to be activated prior to running procmgr; lots of moving parts
Solution #3: include the path in cnf file
Pro: avoids hardcoding of path; enables user to adjust
Con: adds clutter to every cnf file; enables user to get it wrong
Solution #4: include the path in a static procmgr configuration file
Pro: avoids hardcoding of path; enables sysadmin to adjust; /etc/procmgrd.conf exists today
Con: /etc/procmgrd.conf historically not present on LCLS operator consoles; /etc is not the best directory choice
I prefer solution #4. How about you? |
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
Solutions #4 or #3 would be my preference. |
...
Overview
Content Tools