DOCSLIB.ORG

Installing Conserver

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Installing Conserver Installing Conserver version 1.0 David K. Z. Harris zonker@certaintysolutions.com Bryan Stansell bryan@certaintysolutions.com http://www.certaintysolutions.com/consoles/LISA2K-2.zip http://www.conserver.com/consoles/LISA2K-2.zip © 2000 Certainty Solutions, Inc. Pg. 1 This presentation is a supplement to my console services web pages located at http://www.certaintysolutions.com/consoles/LISA2K-2.zip. These pages have a substantial amount of information noted below each slide. We do this to help minimize the amount of note-taking that you need to do in class, and this should give you more time to listen to the instructors. If you feel that you learn better by taking notes, please feel free to do so. This presentation is meant to be a follow-up to a Basic Serial presentation. While this presentation can stand on its own, there is only a small amount of review of the earlier topic. During this tutorial, we will be discussing the topic of Console Servers as a generic application, but our technical emphasis will be on the Conserver application, which is freely available from http://www.conserver.com/. For most purposes in this tutorial, “Console Server” and “Conserver” can be used interchangeably. ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 1 Pertinent Job History Ø Network Equipment Technologies ² (Comdesign, Bridge Communications) Ø Telebit Corp. Ø Cisco Systems, Inc. Ø Apple Computer, Inc. Ø Synopsys, Inc. Ø Global Networking & Computing ² (We’re now Certainty Solutions.) © 2000 Certainty Solutions, Inc. Pg. 2 Before moving into networking, David Harris was a hardware hacker, working in repair and R&D roles. He has been tinkering with serial devices for more than a decade. “My experience, plus reading plenty of manuals, has taught me that there are a few safe bets that you can make when working with unknown serial devices. I’ve also learned a few tricks that make the job of connecting serial devices to terminal servers easier. I’ll share these tricks throughout this presentation.” Bryan Stansell is a Systems Administrator, and has been programming for many years, as an extension to his systems administration tasks, because he enjoys programming. Bryan has been the keeper of the Conserver application for more than five years, having taken on the program while working for Arnold De Leon at Synopsys, Inc., and he’ll help answer questions related to the Conserver application and client software. Bryan was one of the original employees of Global Networking & Computing (GNAC, Inc.), more than 4 years ago. David Harris has been with the company for nearly three years. In August 2000, GNAC became Certainty Solutions. ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 2 Remember the Serial talk? Ø Why console ports are good Ø The benefits of terminal servers Ø Making serial connections easy Ø Review various architecture models Ø Where to find information © 2000 Certainty Solutions, Inc. Pg. 3 Terminal servers can allow us to provide remote access to console ports around the network, and this allows us to respond faster to outage/problem alerts, thus reducing the duration of outages/problems. While terminal servers can be costly to deploy, their advantages can offset those costs, especially when downtime has financial impact! We took away a lot of the mystery surrounding serial connections, and discussed tools and accessories that can help make connecting various devices a lot easier. We also illustrated how to make and test those new connections, and explained why those methods work so well, and why they will save you time. We looked at various architectures for deploying terminal servers in different areas of both large and small networks. (We'll review those architectures in this session, this time with console servers in mind.) ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 3 Terminal Servers help reach Ø One terminal server can support many devices in one area. Ø Connections are costly, but can be worth it! Ø Saves time running between data centers. Ø Cheaper than extending many serial lines. © 2000 Certainty Solutions, Inc. Pg. 4 If you have a bunch of devices at a remote location, you likely have a network already in place for the devices. Usually these are hosts in a remote data center, but they could include network gear in wiring closets, or even a remote site with telemetry and control equipment. In these cases, the terminal server becomes one more addressed device on the network, and it can connect to dozens of devices at one time. The cost for a 10/1000 switch port is currently cheaper than a serial port some of the expensive terminal servers. However, the costs for the serial ports are beginning to drop. (And they are still cheaper than gigabit ethernet ports!) The value of deploying terminal servers is from the reduced downtime because technical staff can fix problems more quickly when they can get to the consoles of ailing devices more quickly. You can use serial extenders, if you have plenty of fiber between the main and remote console locations, but that fiber has value to you as well, which affects your cost equation. ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 4 Terminal Server Review Ø How terminal servers provide access ² Reverse Telnet • Workstation telnet to TS address:port • 7-bit session? 8-bit clean? • Can you escape from the session? ² Vendor-specific port formulae • Different ranges for 7-bit, 8-bit... ² Vendor-specific features © 2000 Certainty Solutions, Inc. Pg. 5 Originally, modems or ‘dumb terminals’ were connected to terminal servers, and users would telnet from the terminal server to other points around the network. Today, most terminal servers allow you to open a socket-based connection to the IP address of the terminal server, but at a high TCP port number, to connect to a particular serial port. Some vendors allow only 7-bit sessions, while others provide the option for full 8-bit sessions, and even “non-escapable” sessions (where the attached device needs to drop the DCD or hardware handshake lead to disconnect you session). The list below tells you the formulae to determine the TCP port number for two of the more popular terminal servers (where ‘n’ is the line (serial port) number you wish to connect). Cisco: 2000 + n Xyplex: 2000 + (100 * n) IOLAN: 10000 + n ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 5 Terminal Server Advantages Ø Admin can operate many consoles at once Ø One port per telnet session Ø Easy to cut-and-paste between session windows Ø Many admins can work on different machines at once ² Admin A works on server 4 ² Admin B works on a router © 2000 Certainty Solutions, Inc. Pg. 6 It’s common to open many windows to different ports, so you can copy and paste between them. Many administrators can work with different hosts simultaneously, from different workstations, rather then waiting in line to use a shared terminal or laptop. Only one person can be connected to each port at any given time. This is normally a good thing, as it can prevent two administrators from making configuration changes at the same time, providing that you make it a policy to make changes from the serial console. If another person tries to connect to a busy port, the connection is refused, with a message to the user. There is a downside to this, however, in the case that one administrator connects to a port, and then goes to lunch, or home. With the idle session still connected, nobody else can connect to that same port. (Someone with administrator privileges on the terminal server needs to log onto the terminal server, and reset that serial port to break the connection.) ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 6 What We’ll Cover Today Ø Things to consider… Ø Review architecture models Ø Where to find conserver Ø Costs and features Ø Installation and configuration Ø Suggested operational practices Ø Questions and Answer session © 2000 Certainty Solutions, Inc. Pg. 7 This tutorial usually follows a Basic Serial tutorial, and so the next few slides would be a basic review of material covered before the break. As a result, we’ll probably cover them pretty quickly. If this tutorial is being offered as a stand-alone session, we’ll spend more time covering security concerns, and explaining the architectures. We also want to know what you expect from the class, and we’ll explain how we think we can cover the topics. During the tutorial, we’ll also invoke a demo of conserver to help illustrate certain aspects of the application and user interface. ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 7 Things to Consider Ø Time synchronization Ø Security & Network Concerns Ø Is serial BREAK a problem? Ø Change Control Aspects Ø Distributed logging © 2000 Certainty Solutions, Inc. Pg. 8 If you will be using your logs to troubleshoot, you should ensure that all of the machines have synchronized clocks. Determine which network(s) will host the terminal servers. Is your deployment in compliance with any existing security policies? (You may not be able to connect to certain networks, or you may not be allowed to extend those networks into any other non-secure areas.) You may plan to put the terminal servers on the management network for security reasons.
Load more

Recommended publications
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • Muxserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002
    MUXserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002 2nd Edition Second Edition - February 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation (Australia) Pty. Limited. Digital Equipment Corporation (Australia) Pty. Limited assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation (Australia) Pty. Limited or its affiliated companies. Copyright ©1992 by Digital Equipment Corporation (Australia) Pty. Limited. All Rights Reserved. Printed in Australia. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem UWS DEC/MMS IAS VAX DECnet MASSBUS VAXcluster DECstation PDP VMS DECsystem–10 PDT VT DECSYSTEM–20 RSTS DECUS RSX DECwriter ULTRIX dt Contents Preface viii Chapter 1 Introduction 1.1 Overview of the MUXserver 380 Network . ................................1–1 1.2 Typical MUXserver 380 Network Configuration ...............................1–2 1.3 The MUXserver 380 . .................................................1–3 1.4 Connecting the MUXserver 380 . ........................................1–6 1.5 Installation Overview . ................................................1–10 1.6 Items Required for MUXserver 380 Installation .............................1–11 1.7 Service Options ......................................................1–12 1.7.1 Digital On-Site Service .
    [Show full text]
  • Decserver 90M Installation Guide
    DECserver 90M Installation Guide Part Number: IG-DSRVH-00 April 2002 This document describes how to install and troubleshoot the DECserver 90M. Revision/Update Information: This is a new document. Digital Networks makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital Networks or an authorized sublicensor. Copyright © 2001 DNPG, LLC (“Digital Networks”). All rights reserved. Digital Networks 486 Amherst St. Nashua , NH 03063-1224 Web site: www.digitalnetworks.net Digital Networks is the tradename of DNPG, LLC, and is not affiliated with Compaq Computer Corporation. DIGITAL, the Digital Logo and DEC are used under license from Compaq Computer Corporation. clearVISN, Multistack, MultiSwitch, and ThinWire are trademarks of Cabletron Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. NOTICES FCC Notice — Class A Computing Device: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
    [Show full text]
  • ETS4P4 Terminal Server
    ETS4P4 Terminal Server Installation Guide Thank you for purchasing this Lantronix ETS Ethernet Terminal Server. As the newest addition to our successful Ethernet terminal server family, the ETS uses software for multiprotocol Ethernet connections that has over 5 years of real-world feedback and de- velopment behind it. Lantronix is constantly improving the capabilities of our prod- ucts, and we encourage you to take advantage of new features through our FREE software upgrades (available via ftp over the Internet or BBS.) Our Flash ROM products, including this ETS, provide the sim- plest means for upgrades and installation. I hope you find this manual easy to use, and thorough in its explanation of the power- ful features you can now access on your network. Brad Freeburg President Contents 1 Introduction Overview...........................................................................1-1 Configuration ................................................1-1 Software ..........................................................1-2 About the Manuals ..........................................................1-2 2 Installation Overview...........................................................................2-1 ETS Components..............................................................2-1 Installation ........................................................................2-2 Selecting a Location for the ETS ..................2-2 Connecting to the Ethernet...........................2-2 Connecting a Terminal..................................2-3
    [Show full text]
  • Configuring Asynchronous Lines and Interfaces
    Configuring Asynchronous Lines and Interfaces This chapter describes how to configure asynchronous line features in the following main sections: • How to Configure Asynchronous Interfaces and Lines • How to Configure Other Asynchronous Line and Interface Features • Configuration Examples for Asynchronous Interfaces and Lines Perform these tasks, as required, for your particular network. To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the “Identifying Supported Platforms” section in the “Using Cisco IOS Software” chapter. For a complete description of the commands in this chapter, refer to the Cisco IOS Dial Technologies Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online. How to Configure Asynchronous Interfaces and Lines To configure an asynchronous interface, perform the tasks described in the following sections as required: • Configuring a Typical Asynchronous Interface (As required) • Creating a Group Asynchronous Interface (As required) • Configuring Asynchronous Rotary Line Queueing (As required) • Configuring Autoselect (As required) Configuring a Typical Asynchronous Interface To configure an asynchronous interface, use the following commands beginning in global configuration mode: Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Command Purpose Step 1 Router(config)# interface async number Brings up a single asynchronous interface and enters interface configuration mode. Step 2 Router(config-if)# description description Provides a description for the interface.
    [Show full text]
  • SSH Terminal-Line Access
    SSH Terminal-Line Access The SSH Terminal-Line Access feature provides users secure access to tty (text telephone) lines. tty allows the hearing- and speech-impaired to communicate by using a telephone to type messages. • Finding Feature Information, page 1 • Prerequisites for SSH Terminal-Line Access, page 1 • Restrictions for SSH Terminal-Line Access, page 2 • Information About SSH Terminal-Line Access, page 2 • How to Configure SSH Terminal-Line Access, page 3 • Configuration Examples for SSH Terminal-Line Access, page 5 • Additional References, page 6 • Feature Information for SSH Terminal-Line Access, page 7 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for SSH Terminal-Line Access Download the required image to your router. The secure shell (SSH) server requires the router to have an IPSec (Data Encryption Standard (DES) or 3DES) encryption software image from Cisco IOS Release 12.1(1)T or a later release. The SSH client requires the router to have an IPSec (DES or 3DES) encryption software image from Cisco IOS Release 12.1(3)T or a later release.
    [Show full text]
  • Single-Port Terminal Server Model 2120
    Device Servers Single-Port Terminal Server Model 2120 The Patton Model 2120 Single Port Terminal Server brings RS-232 serial devices onto the LAN using the flexibility of Ethernet and TCP/IP protocols. Control and Monitor Serial Devices thernet continues to be the most com- user-defined IP address and port. Once con- Control and monitor your RS-232 asynchronous mon office networking infrastructure. nected to the remote host, data is passed terminals and devices over the local area network ENow, Ethernet is making its way from transparently end-to-end. The built-in DHCP the office to the shop floor. Traditional RS- Client allows the Model 2120 to dynamically Supports a Wide Range of Data Rates 232 environments require the use of multi- obtain an IP address and a subnet mask from User-selectable async data port serial cards, expensive cables, and the a master server. With SLIP and PPP connec- rates up to 115.2 kbps personnel to manage multiple systems. tions, remote users can Patton’s Model 2120 Single Port Terminal access the network and it Connects Directly to the LAN Server provides a quick, simple, and cost will appear as if they were 802.3 10Base-T LAN connection effective solution for connecting traditional locally connected. via RJ-45 connects to any hub/switch RS-232 terminals and devices to the LAN. Why go to the expense and hassle of installing Special Rates Available Standard TCP/IP Protocols Supported The Model 2120 enables you to bring all sys- Call for Details TCP, UDP, IP, ICMP, TELNET, ARP, DHCP, tems and equipment together onto one local outdated multi-port serial FTP, SLIP, PPP, DNS, WINS, and PAP area network.
    [Show full text]
  • An Introduction to Security in a CSM 1.3 for AIX 5L Environment
    Front cover An Introduction to Security in a CSM 1.3 for AIX 5L Environment Peek at the latest security mechanisms for pSeries clusters Practical security considerations included Security concepts and components explained Octavian Lascu Rashid Sayed Stuart Carroll Teresa Coleman Maik Haehnel Petr Klabenes Dino Quintero Rogelio Reyes, Jr. Mizuho Tanaka David Duy Truong ibm.com/redbooks International Technical Support Organization An Introduction to Security in a CSM 1.3 for AIX 5L Environment December 2002 SG24-6873-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (December 2002) This edition applies to Version 1, Release 3, of IBM Cluster Systems Management for use with the AIX operating system Version 5, Release 2. © Copyright International Business Machines Corporation 2002. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . vii Notices . .ix Trademarks . x Preface . .xi The team that wrote this redbook. .xi Become a published author . xiii Comments welcome. xiii Chapter 1. Introduction . 1 1.1 Security overview . 2 1.1.1 System security. 2 1.1.2 Network security basics . 3 1.1.3 Data transmission security . 4 1.2 Cluster Systems Management security basics . 5 1.2.1 Reliable Scalable Cluster Technology (RSCT) . 6 1.2.2 Resource Monitoring and Control (RMC) . 6 1.2.3 Resource managers (RM). 7 1.2.4 Cluster Security Services (CtSec). 7 1.2.5 Group Services and Topology Services . 8 Chapter 2.
    [Show full text]
  • Managing Serial Devices in a Networked Environment
    Managing Serial Devices in a Networked Environment Lantronix, Inc. 15353 Barranca Parkway Irvine, CA 92618 Tel: +1 (949) 453-3990 Fax: 1+ (949) 453-3995 Introduction The proliferation of network management technology in both hardware and software has provided the network manager with an extensive tool kit. Still, many devices being used today support only serial management. Such devices provide a serial management port for attaching terminals or PCs to perform management functions. These serial-only devices may also require the network manager to implement costly and sometimes cumbersome workarounds to be included in the management scheme. This paper explores the technological advances in Device Server design that make it possible to manage serial-only devices over a network. Management via Serial Communications: Non-networked Techniques Networked communication seems like a birthright to current PC users. However, one should remember that for many years serial communication was the only way to transmit data from one device to another. Many industrial, medical and monitoring devices were designed long before the current advancements in integrated circuits made Ethernet technology so inexpensive. Some of these devices would even qualify as legacy equipment, built with internal processing capabilities far below that of current desktop PCs. The only management option provided on many of these products is a serial port. Usually RS-232, this port is intended to connect directly to a PC or dumb terminal which displays device status information and/or grants access to device configuration information. In some cases, the PC is tasked with processing raw data sent over the serial port, due to the fact that the device itself does not have the bandwidth to do so.
    [Show full text]
  • Openvms I/O User's Reference Manual
    OpenVMS I/O User’s Reference Manual Order Number: AA–PV6SD–TK April 2001 This manual contains the information necessary to interface directly with the I/O device drivers supplied as part of the Compaq OpenVMS operating system. Several examples of programming techniques are included. This document does not contain information on I/O operations using the OpenVMS Record Management Services. Revision/Update Information: This manual supersedes the OpenVMS I/O User’s Reference Manual, OpenVMS Alpha Version 7.2, OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the United States and other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein.
    [Show full text]
  • IOLAN Electric Utility Terminal Server
    IOLAN Electric Utility Terminal Server perle.com/products/electric-utility-terminal-server.shtml 8, 16 and 32 serial ports on RJ45 - software selectable RS232/422/485 Advanced security features for NERC CIP critical cyberasset substation compliance Substation hardened for harsh electrical utility and industrial applications Universal high voltage power supply: nominal 125v DC / 250v DC or 115v AC / 230v AC Dual Feed low voltage power supply: nominal 24v DC /48v DC Dual 10/100/1000 Ethernet with Redundant Path Technology Built-in failsafe alarm relay Electrical utility engineers and project managers that require a cost effective serial-to-Ethernet solution to help meet NERC-CIP compliance for the protection of critical cyberassets in substations must consider the IOLAN SDS HV/LDC Terminal Server. In addition to the most extensive security features available, these IOLAN’s are designed to meet harsh environments associated with Power Substations with attributes such as support for substation AC and DC voltage ranges, extended operating temperatures and meeting emission, immunity and safety approvals associated with substation IT equipment. Ideal for Electrical utility engineers and Project Managers requiring a high performance serial to Ethernet interface for serial RS232 or RS485 based devices such as SCADA based RTUs and protection relays. Environments that require a serial terminal server with unique environmental, form factor, or power inputs in harsh environments Substation Automation projects where using secured communications in remote
    [Show full text]
  • Université De Montréal Low-Impact Operating
    UNIVERSITE´ DE MONTREAL´ LOW-IMPACT OPERATING SYSTEM TRACING MATHIEU DESNOYERS DEPARTEMENT´ DE GENIE´ INFORMATIQUE ET GENIE´ LOGICIEL ECOLE´ POLYTECHNIQUE DE MONTREAL´ THESE` PRESENT´ EE´ EN VUE DE L’OBTENTION DU DIPLOMEˆ DE PHILOSOPHIÆ DOCTOR (Ph.D.) (GENIE´ INFORMATIQUE) DECEMBRE´ 2009 c Mathieu Desnoyers, 2009. UNIVERSITE´ DE MONTREAL´ ECOL´ E POLYTECHNIQUE DE MONTREAL´ Cette th`ese intitul´ee : LOW-IMPACT OPERATING SYSTEM TRACING pr´esent´ee par : DESNOYERS Mathieu en vue de l’obtention du diplˆome de : Philosophiæ Doctor a ´et´edˆument accept´ee par le jury constitu´ede : Mme. BOUCHENEB Hanifa, Doctorat, pr´esidente M. DAGENAIS Michel, Ph.D., membre et directeur de recherche M. BOYER Fran¸cois-Raymond, Ph.D., membre M. STUMM Michael, Ph.D., membre iii I dedicate this thesis to my family, to my friends, who help me keeping balance between the joy of sharing my work, my quest for knowledge and life. Je d´edie cette th`ese `ama famille, `ames amis, qui m’aident `aconserver l’´equilibre entre la joie de partager mon travail, ma quˆete de connaissance et la vie. iv Acknowledgements I would like to thank Michel Dagenais, my advisor, for believing in my poten- tial and letting me explore the field of operating systems since the beginning of my undergraduate studies. I would also like to thank my mentors, Robert Wisniewski from IBM Research and Martin Bligh, from Google, who have been guiding me through the internships I have done in the industry. I keep a good memory of these experiences and am honored to have worked with them. A special thanks to Paul E.
    [Show full text]