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: Start IOC automatically at boot |
From: | Donny Domagoj Cosic via Tech-talk <tech-talk at aps.anl.gov> |
To: | tech-talk at aps.anl.gov |
Date: | Fri, 07 Jan 2022 21:57:44 +0100 |
Hi Ralph,Thank you for bringing this to my attention. It looks like a very nice solution. Being relatively new to epics, I sometimes get lost in the TechTalk discussions.
Regards, --- Donny Domagoj Cosic Laboratory for Ion Beam Interactions Ruđer Bošković Institute Bijenička cesta 54 | HR-10 000 Zagreb | CROATIA T: +385 1 4561 041 | @: dcosic at irb.hr | www.irb.hr Dana 07.01.2022 09:37, Ralph Lange via Tech-talk je napisao(la):
On Fri, 7 Jan 2022 at 00:15, Hu, Yong via Tech-talk <tech-talk at aps.anl.gov> wrote:As long as you use “sudo manage-iocs start myIOC” to start your IOC and “sudo manage-iocs stop myIOC” to stop your IOC, the Python process "python your-python-file.py" should be automatically terminated when the IOC is stopped.I wouldn't regard such a setup as robust enough for production use. You might also want to look at solutions like pyDevSup [1] which can run Python code *inside* your IOC - at least that was a promising answer when the original question was discussed on TechTalk in 2019 [2]. (Yes, TechTalk has a search function, and I used it to find that link.) Cheers, ~Ralph [1] http://mdavidsaver.github.io/pyDevSup/ [1] [2] https://epics.anl.gov/tech-talk/2019/msg01678.php [2] Links: ------ [1] http://mdavidsaver.github.io/pyDevSup/ [2] https://epics.anl.gov/tech-talk/2019/msg01678.php