| 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: | Fwd: Re: Using a terminal server to catch boot messages |
| From: | "Pete R. Jemian" <[email protected]> |
| To: | [email protected] |
| Date: | Tue, 06 Nov 2001 17:04:24 -0600 |
>>>>> "Brian" == Brian McAllister <[email protected]> writes: Brian> Are those of you using "console logging" (through xterms or other) Brian> using this instead of the EPICS iocLogServer ?
The iocLogServer does not catch all the messages we want to log. The wrap-around log feature is not so useful when it comes to diagnosing boot problems and other diagnostics that generate console output which does not go through the error logging mechanisms.
Brian> Other than possibly missing something coming from VxWorks itself, Brian> is there any reason why direct logging of the console is necessary
Jim Thomas wrote: We'd kind of like to see VxWorks messages :-) Plus the subject was "boot messages" so that kind of implied needing the console messages.
Absolutely. When things are OK, the iocLogServer is sufficient. All too often, things are not that OK.
Pete Jemian UNICAT