Page History
...
Code Block | ||||
---|---|---|---|---|
| ||||
If #2 doesn’t work, then I think you’ve convinced me to change my vote to #4 (keeps the cnf file clean). |
Procmgr: how to handle RELDIR and TESTRELDIR env vars?
(10/8/2018)
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
if RELDIR is defined you get:
PATH=$RELDIR/bin
if TESTRELDIR is defined you get
PATH, LD_LIBRARY_PATH, PYTHONPATH
If both are defined, you get all of the above, with TESTRELDIR taking precedence over RELDIR in PATH. |
DAQ packaging changes, and cnf/procmgr tweaks
...
I can determine the current conda release version from my environment. Why does procmgr need it configured in cnf files?
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
Not everyone has the same use case. A developer typically runs procmgr after activating conda, but others invoke might procmgr directly.
For example, LCLS hutches start procmgr from desktop icons.
Not every process requires conda. The conda keyword identifies a procmgr process as requiring conda.
Procmgr supports remote processes. Processes running remotely see environment variables defined remotely,
these variables differ from what you observe locally.
When deployed at LCLS, relying on environment variables can complicate determining exactly which DAQ release is running.
We avoid relying on environment variables when possible. |
Overview
Content Tools