On Friday, March 15, 2013 11:58:54 you wrote:
> Hi Ben- I'm going direct to the source; if you think this would interest
> the community,
> feel free...
I think this is of general interest.
> What's the correct way to "suspend" a sequencer thread, e.g. when it
> encounters a condition where it can't go on?
There is currently no built-in feature to support that, but see below.
> In the past I've usually just printed a message and gone
> into "hibernation" by spinning in a state which just delays forever.
> The disadvantage
> there is that there's no external indication that something's wrong; it
> would be better
> if for ie. VxWorks the thread actually had a SUSPEND status so it
> triggers an alarm.
> On the other hand, I don't want to suspend the entire seq runtime, just
> that one state set. This is for EPICS 3.14, so OSI.
I'd say you just call epicsThreadSuspendSelf from the program when you detect
an irrecoverable error. It could be you need to add a line
%%#include "epicsThread.h"
to the program (before the first state set is declared).
Would that suit your purposes?
Cheers
--
Ben Franksen
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachm€nts
Attachment:
signature.asc
Description: This is a digitally signed message part.
- Navigate by Date:
- Prev:
Breakpoint tables status and usage in EPICS Abadie Lana
- Next:
EPICS CSS JAAS Authentication with LDAP Xinyu.Wu
- 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: Breakpoint tables status and usage in EPICS Andrew C. Starritt
- Next:
EPICS CSS JAAS Authentication with LDAP Xinyu.Wu
- 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
|