Why is CONDABASE defined in /etc/procmgrd.cnf?
Multiple options were discussed. Solution #4 was eventually chosen. (October 2018)
Chris Ford writes
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?
Clemens Weninger writes
Solutions #4 or #3 would be my preference.
Chris O'Grady writes
If #2 (the ideal solution) is proving to be difficult, I think I would vote for #3. Solution #4 (procmgrd.conf) feels strange to me, but I could be convinced.
Chris Ford writes
Regarding #4, we can adjust the file name and location if they are a problem. I recall that Amedeo preferred a location other than /etc for such configuration files. But that was years ago, and neither Amedeo nor I recall the exact details. Whatever the file name, here are the seldom-changing parameters it currently holds: # procmgrd.conf PORTBASE=29000 PROCMGRDBIN=/reg/common/package/procServ/2.6.0-SLAC/x86_64-rhel7-gcc48-opt/bin/procmgrd PROCMGRDUSER=nobody
Chris O'Grady writes
If #2 doesn’t work, then I think you’ve convinced me to change my vote to #4 (keeps the cnf file clean).
Overview
Content Tools