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: Console access and managing soft IOCs |
From: | Steve Lewis <[email protected]> |
To: | "Pearson, MR (Matthew)" <[email protected]> |
Cc: | [email protected] |
Date: | Thu, 12 Feb 2009 07:01:24 -0800 |
At 3:39 PM +0100 2009/02/12, Ralph Lange wrote:
provServ runs the IOC and provides access through local telnet.conserver provides the common interface to both soft and VME IOCs, handles user authentification, read-only vs. read/write access, time stamped logging, playback of recent console output (without screwing up the log file), and more.
At 1:45 PM +0000 2009/02/12, Pearson, MR (Matthew) wrote:
Hi, Thanks. Yes, I'm not sure we would need to use conserver if we had procServ. I get the impression that the only reason other sites had the IOC->procServ->conserver layering was to preserve to conserver interface. Cheers, Matthew-----Original Message----- From: Mark Rivers [mailto:[email protected]] Sent: 12 February 2009 12:59 To: Pearson, MR (Matthew); [email protected] Subject: RE: Console access and managing soft IOCs We recently started using procServ for both our VME IOCs and soft IOCs. It's great, since multiple users can be seeing the console at once, and logging is done. The VME IOCs are connected to terminal servers, so the procServ process for
> them is a telnet session to the particular terminal server port.