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: Creating a database record |
From: | "Dudley, David via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 15 Feb 2022 14:40:33 +0000 |
Would it be possible to perform this function from inside the iocInit function chain? When iocInit(0) is performed, I install an init function hook to receive
all the init steps. Could I build and install a database during – say- the initHookAfterInitDevSup announcement? At that point, I push a database out to a temp file, and the load it in using a call to dbReadDatabaseFP, or similar? This is just to make a couple of statistics records available every time the driver loads, but I could see other uses for it. Later-
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Ralph Lange via Tech-talk [EXTERNAL] This email originated from outside of FRIB
On Thu, 3 Feb 2022 at 21:01, Dudley, David via Tech-talk <tech-talk at aps.anl.gov> wrote:
I know of a driver that does that, yes. In the initialization of the driver (started by calls from the startup script) they detect the hardware and create a matching DB file in '/tmp', then load that file. Works fine. I don't like that for a production system for multiple reasons. Having no or little control over which records an IOC loads.... Broken cards that would just disappear from the name space with no trace.... But I see the advantage for plug-and-play lab use. If you don't hard code the records into the driver code, but maybe blow up from templates that are part of your application, you would give the user at least some control. Cheers, |