Hi Mark,
On Thursday 11 March 2010 08:51:36 Mark Rivers wrote:
>
> One way to avoid this is to always restart your vxWorks IOC with the
> "reboot" command. That will cause the EPICS exit handlers to be called.
> Recent versions of asyn install EPICS exit handlers which will cleanly
> close all TCP sockets, and EPICS CA also closes things cleanly. Even if
> you need to power off the vxWorks system, you should first type "reboot",
> then power it off. This will close the sockets cleanly.
Actually this will only work if you have a specific modification to your
vxWorks BSP which ensures that the epicsAtExit() handlers get called before
the network shuts down. Note that a Control-X reboot will also cause these to
run.
The patch requires registering a rebootHook() early in the BSP startup process
before the network is initialized. I described it in the tech-talk message
here: http://www.aps.anl.gov/epics/tech-talk/2005/msg00004.php
- Andrew
--
The best FOSS code is written to be read by other humans -- Harald Welte
- References:
- RE: IP asyn timeout connection Mark Rivers
- Navigate by Date:
- Prev:
RE: IP asyn timeout connection Mark Rivers
- Next:
RE: IP asyn timeout connection Mark Rivers
- 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: IP asyn timeout connection Mark Rivers
- Next:
RE: IP asyn timeout connection Mark Rivers
- 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
|