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. | 