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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: getting streamDevice exception handler replyTimeout to write to a record [SEC=UNCLASSIFIED] |
From: | "CORNALL, Terry via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 1 Apr 2020 02:20:05 +0000 |
For the record, I’ll put a nice answer here that I got from James Larson. ‘At the end of your exec statement direct the output, >, to /dev/null . It won’t show up on the ioc .’ I tried that and it works a treat. In the protocol file: commsFail { #exec 'echo "comms fail on \$0"'; #Turn this off in production exec 'dbpf \$1:\$4 "Comms error"> /dev/null'; #/dev/null makes it silent } readCurrent{ …. Usual out and in stuff, then an exception handler for timeout @replytimeout{commsFail;} #comms is down } And in the database file: …. field(INP, "@$(DEVICE).proto readCurrents($(P)$(R),ITIME_MON,OVR_STS,COMMSFAIL) $(PORT) 0") ….. Thanks James. |