1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [EXTERNAL] Phoebus Archive xml config file: Automate generation, using Autosave module of synApps?? |
From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Kuldeep Joshi <kuldeep.joshi at gmail.com> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 28 Jul 2021 12:33:30 +0000 |
> I wonder if leveraging the function makeAutosaveFileFromDbInfo from the autosave module is used, one may not have to worry about macro substitution.
Correct, if you create some makeArchiveConfigFile("/path/to/config.xml") tool for the IOC, you could use the info field support code in EPICS base to get the information, invoke it in st.cmd, so after each IOC reboot you'd have an archive config file for the
IOC.
At the time we were looking for a tool that runs on the host, at the time you "make" the IOC software. But you can't archive anything unless the IOC is running,
so requiring the IOC to start first is actually somewhat logical.
-Kay
|