| 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 <2025> | 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 <2025> |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Help with bumpless IOC reboot, record linking and initialization concepts |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "Johnson, Andrew N." <anj at anl.gov> |
| Cc: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
| Date: | Thu, 18 Sep 2025 10:10:34 -0700 |
|
On 9/18/25 07:54, Johnson, Andrew N.
via Tech-talk wrote:
Many of our IOCs use one or more “dbpf” commands in their startup script (sometimes after an epicsThreadSleep) ... Nooooooo! Finding a bunch of random, rarely commented, dbpf calls in an IOC
start script is to me a bad code smell. The same goes for sleeps,
only more so. Please investigate 'field(PINI, "RUNNING")', or
look at other ways to actually synchronize startup.
... it should even be possible to handle disconnections and later reconnections for links to remote IOCs if you want to do that. imo. any well written driver for an ethernet attached device
__needs__ to do this. Generally, I have found that the more effective way to coordinate
connect/disconnect is at the driver level. Generally with a
special device support to drive on-connect processing.
|