| 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: | "Al Honey" <[email protected]> |
| To: | "Thompson, David H." <[email protected]>, <[email protected]> |
| Date: | Thu, 1 Mar 2007 10:59:49 -1000 |
|
Aloha At Keck our IOC console ports are all
connected to terminal server ports and, typically, there is a telnet session to
each of those ports that are ‘tee’d to a log file. The reason for
this is that software bugs (typically in drivers or callbacks) will often cause
VxWorks failures which may generate messages that do not get into the iocLog
files. I suspect it should be easy to adapt the iocConsole/screen software to
deal with the terminal server sessions (thanks for that info). Cheers, Al 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? |