On Jul 1, 2009, at 8:04 AM, Mark Rivers wrote:
David,
The medm message is "normal" because your IOC is exiting for some
reason. You need to find the reason for that. It's strange that
the IOC exits with no message, so it may be a bit difficult to track
down. It have not seen that. Some systems are set up with an
inactivity timer that will log you out after some period of
inactivity, but that should kill your ssh session, not just the IOC
application.
If the IOC is terminating unexpectedly you should try running it under
GDB and capture what's going on.
--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793
- References:
- medmCAExceptionHandlerCb: Channel Access Exception message David Kline
- RE: medmCAExceptionHandlerCb: Channel Access Exception message Mark Rivers
- Navigate by Date:
- Prev:
RE: medmCAExceptionHandlerCb: Channel Access Exception message Mark Rivers
- Next:
Re: Prodex MAXv command responses (RA, QA, EA, RL) for different versions of firmware Ron Sluiter
- 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: medmCAExceptionHandlerCb: Channel Access Exception message Mark Rivers
- Next:
CA environment variables not being set? Shawn Smith
- 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
|