| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~epics-core/epics-base/+git/Com:errlog2syslog into epics-base:7.0 |
| From: | Martin Konrad via Core-talk <[email protected]> |
| To: | mdavidsaver <[email protected]> |
| Date: | Tue, 26 Nov 2019 16:29:17 -0000 |
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.
--
https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/373098
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.