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: Best practices for booting IOC at Linux startup? |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Feister, Scott" <scott.feister at csuci.edu> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Wed, 21 Jul 2021 23:23:41 +0000 |
Hi Scott,
In case it wasn’t obvious: Starting IOCs inside tmux or procServ (or GNU Screen as we use at APS) is recommended to allow you to connect to the IOC console and run diagnostic commands using the IOC shell, in case you need to debug issues with
the IOC or its client connections. It is possible to create and run IOCs without a shell, but it provides many commands which can give you information about what it’s doing which you can’t otherwise access remotely.
The procServ package is probably the simplest approach, but it doesn’t give you the ability to scroll back and look at messages that were shown on the IOC console before you connected, like tmux or Screen can. You can have procServ log the console
output to a file though, or if you start it using systemd it could send everything to the systemd journal.
Recent versions of procServ come with support scripts for use with systemd; post here if you have questions about them.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|