Experimental Physics and Industrial Control System
As currently implemented, Channel Access on the IOC tries to communicate
with remote clients/servers when shutting down prior to reboot (this is
inferred from error messages seen during the shutdown). Unfortunately,
network services will always have been shut down first, so these
notification attempts always fail, and will continue to do so unless the
VxWorks reboot processing is modified to allow user hooks to be handled
first, which seems unlikely.
Occasionally, one of our IOCs will hang on reboot, requiring physical
access to push the reset button. I am wondering if this hang might in part
be due to the system trying to do things while in a partially shut down
state, and if there is any reason not to eliminate the CA server behavior
noted above, on the chance that it may be contributing to the problem.
Or perhaps, EPICS could have a "shutdown" routine, which terminates the
EPICS tasks appropriately, and then calls reboot ?
----
Brian McAllister Controls Programmer/Beam Physicist
[email protected] MIT-Bates Linear Accelerator
(617) 253-9537 Middleton, MA
- Replies:
- RE: channel access reboot behavior Jeff Hill
- Re: channel access reboot behavior Paul Sichta
- Navigate by Date:
- Prev:
RE: Newbie question: example Application Jeff Hill
- Next:
RE: channel access reboot behavior Jeff Hill
- 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
- Navigate by Thread:
- Prev:
RE: Newbie question: example Application Jeff Hill
- Next:
RE: channel access reboot behavior Jeff Hill
- 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