| 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: Serial port access and loging services for IOCs? |
| From: | "Jeff Hill" <[email protected]> |
| To: | "'Thompson, David H.'" <[email protected]> |
| Cc: | <[email protected]> |
| Date: | Thu, 1 Mar 2007 14:07:04 -0700 |
|
Ø Here at SNS we have lately had problems with IOCs crashing without leaving any trail for Ø analyzing what the problem was
For Linux IOC’s I would build debug and turn on core file production. For vxWorks I understand that vxWorks 6.0 introduces capabilities to debug crash files post mortem, but I currently don’t have personal experience with that new feature.
Jeff
From: Thompson, David
H. [mailto:[email protected]]
Here at SNS we have lately had problems with IOCs crashing without leaving any trail for analyzing what the problem was. We have our own home grown procServe and we are looking into the iocConsole/screen software that SLAC is using. We are different from SLAC in that we use Digi port servers with a driver on one of the linux servers that maps port server ports into local /dev/ttyXXNNN devices. We just use 'cu' to open a serial port. IocConsole does not support that but making it do so would not be hard I don't think.
Looks like a modified iocConsole is our best option but before we commit to it we thought we out to see what others are doing to capture the last few lines of terminal activity from running and crashed hard IOCs.
Any ideas?
|