It looks like I completely mis-read this code in asCa.c
and thought that asCaStop() was actually causing the worker to break.
It isn't.
I've reverted this change with bac8851132b28579dd9d85a3f0deed08f8d9a0b1
** Changed in: epics-base
Assignee: (unassigned) => mdavidsaver (mdavidsaver)
** Changed in: epics-base
Milestone: None => 7.0.3.2
** Changed in: epics-base
Importance: Undecided => Medium
** Changed in: epics-base
Status: New => Fix Committed
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1868680
Title:
Access Security file reload (asInit) fails
Status in EPICS Base:
Fix Committed
Bug description:
Using EPICS Base 7.0.3.1, we observed that calling asInit() from IOC shell never returns and the shell hangs. The IOC continues to respond via CA and PVA but the new rules are not loaded and the shell remains blocked.
The reload operation seems to hang in the asCaStop routine (asCa.c).
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1868680/+subscriptions
- Navigate by Date:
- Prev:
Build failed: EPICS Base base-7.0-564 AppVeyor via Core-talk
- Next:
[Bug 1868486] Re: epicsMessageQueue lost messages mdavidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Build failed: EPICS Base base-7.0-564 AppVeyor via Core-talk
- Next:
[Bug 1868680] Re: Access Security file reload (asInit) fails Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|