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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Making IOC spawn another IOC |
From: | "Marco A. Barra Montevechi Filho via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Shen, Guobao" <gshen at anl.gov>, "Engbretson, Mark S." <engbretson at anl.gov>, "'tech-talk at aps.anl.gov'" <tech-talk at aps.anl.gov> |
Date: | Thu, 25 Aug 2022 19:56:25 +0000 |
No, they are not redundant.
Its more a case of a softIOC that is necessary to the operation of a particular instance of a module, but too specific to be embbeded in the module itself as a whole. So i would like for that particular instance to always come up with the module and the softIOC that controls the module. So i guess wanting an EPICS tool for that was a little naive of me. Thanks 🙂 From: Shen, Guobao <gshen at anl.gov>
Sent: 25 August 2022 10:26 To: Marco A. Barra Montevechi Filho <marco.filho at lnls.br>; Engbretson, Mark S. <engbretson at anl.gov>; 'tech-talk at aps.anl.gov' <tech-talk at aps.anl.gov> Subject: Re: Making IOC spawn another IOC Guess the IOC2 is not redundancy of IOC1? If yes, it would be a topic of redundant IOCs.
Otherwise, as you mentioned, you can use a regular external script, for example a bash script as you mentioned, to monitor for example the heartbeat of IOC1, & IOC2, to do the job.
Thanks, Guobao
From:
Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Tech-Talk <tech-talk at aps.anl.gov>
In the case IOC2 dies the ideal would be IOC 1 respawning it. From: Engbretson, Mark S. <engbretson at anl.gov>
What happens when IOC2 dies? So does IOC 1? Or does IOC1 restart IOC 2? What happens when you have 5 – 10?
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Marco A. Barra Montevechi Filho via Tech-talk
Hello all
Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente. Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately. |