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: How to run IOC in docker containers properly |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Ralph Lange <ralph.lange at gmx.de> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Thu, 18 Jun 2020 18:59:38 +0000 |
On Jun 18, 2020, at 10:58 AM, Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> wrote:
When it’s 3am and you’re diagnosing a problem on an IOC, you’re already connected to its console and you want to see whether the previous boot gave a similar warning message, it’s a lot easier to page up than it is to connect to some other system (which
you probably don’t use very often) just to view the logfile.
We don’t currently keep a permanent record of the console output from our IOCs but that is also on my list to implement for the APS Upgrade. I haven’t decided yet whether to do the logging using procServ or screen. I also want to provide the same interface
to all our IOC consoles, both soft IOCs run under procServ and those that screen connects to via ssh to their terminal server. If I use screen to do the logging then the same logging solution works for both kinds of IOC; if I use procServ I still have to work
out how to log the ssh-connected IOCs.
It’s a risk, but screen has been an essential part of our systems since we started using soft IOCs without our hitting that issue to my knowledge. I don’t have an alternative solution, I assume tmux might behave the same?
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|