Another thought on environment variables vs. commands in st.cmd: At FRIB our IT administrators are running our log servers. They know best which host/port/protocol should be used. They have the tools to provide these settings consistently as environment variables/config files on all machines. I would thus suggest to make it possible for IT to be in control of these settings while IOC engineers are in control of which database files are loaded etc.
to ensure our sysadmins are in control. This works but it would be easier if the IOC would pick up logging settings directly from environment variables.
Another thought on environment variables vs. commands in st.cmd: At FRIB our IT administrators are running our log servers. They know best which host/port/protocol should be used. They have the tools to provide these settings consistently as environment variables/config files on all machines. I would thus suggest to make it possible for IT to be in control of these settings while IOC engineers are in control of which database files are loaded etc.
We are currently doing stuff like
caPutLogInit( "${EPICS_ PUT_LOG_ INET}:$ {EPICS_ PUT_LOG_ PORT}", 1)
to ensure our sysadmins are in control. This works but it would be easier if the IOC would pick up logging settings directly from environment variables.