Oracle Solaris Dynamic Tracing Guide Describes How to Use Dtrace
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
1 Thinking Methodically About Performance
PERFORMANCE Thinking Methodically about Performance The USE method addresses shortcomings in other commonly used methodologies Brendan Gregg, Joyent Performance issues can be complex and mysterious, providing little or no clue to their origin. In the absence of a starting point—or a methodology to provide one—performance issues are often analyzed randomly: guessing where the problem may be and then changing things until it goes away. While this can deliver results—if you guess correctly—it can also be time-consuming, disruptive, and may ultimately overlook certain issues. This article describes system-performance issues and the methodologies in use today for analyzing them, and it proposes a new methodology for approaching and solving a class of issues. Systems-performance analysis is complex because of the number of components in a typical system and their interactions. An environment may be composed of databases, Web servers, load balancers, and custom applications, all running upon operating systems—either bare-metal or virtual. And that’s just the software. Hardware and firmware, including external storage systems and network infrastructure, add many more components to the environment, any of which is a potential source of issues. Each of these components may require its own field of expertise, and a company may not have staff knowledgeable about all the components in its environment. Performance issues may also arise from complex interactions between components that work well in isolation. Solving this type of problem may require multiple domains of expertise to work together. As an example of such complexity within an environment, consider a mysterious performance issue we encountered at Joyent for a cloud-computing customer: the problem appeared to be a memory leak, but from an unknown location. -
Solaris 10 807 Release Notes
Solaris 10 8/07 Release Notes Oracle Corporation 500 Oracle Parkway Redwood City, CA 94065 U.S.A. Part No: 820–1259–13 August 2007 Copyright © 2008, 2011, Oracle and/or its affiliates. All rights reserved. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract,and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). -
An Introduction to the X Window System Introduction to X's Anatomy
An Introduction to the X Window System Robert Lupton This is a limited and partisan introduction to ‘The X Window System’, which is widely but improperly known as X-windows, specifically to version 11 (‘X11’). The intention of the X-project has been to provide ‘tools not rules’, which allows their basic system to appear in a very large number of confusing guises. This document assumes that you are using the configuration that I set up at Peyton Hall † There are helpful manual entries under X and Xserver, as well as for individual utilities such as xterm. You may need to add /usr/princeton/X11/man to your MANPATH to read the X manpages. This is the first draft of this document, so I’d be very grateful for any comments or criticisms. Introduction to X’s Anatomy X consists of three parts: The server The part that knows about the hardware and how to draw lines and write characters. The Clients Such things as terminal emulators, dvi previewers, and clocks and The Window Manager A programme which handles negotiations between the different clients as they fight for screen space, colours, and sunlight. Another fundamental X-concept is that of resources, which is how X describes any- thing that a client might want to specify; common examples would be fonts, colours (both foreground and background), and position on the screen. Keys X can, and usually does, use a number of special keys. You are familiar with the way that <shift>a and <ctrl>a are different from a; in X this sensitivity extends to things like mouse buttons that you might not normally think of as case-sensitive. -
README for X11R7.5 on Netbsd Rich Murphey David Dawes Marc Wandschneider Mark Weaver Matthieu Herrb Table of Contents What and Where Is X11R7.5?
README for X11R7.5 on NetBSD Rich Murphey David Dawes Marc Wandschneider Mark Weaver Matthieu Herrb Table of Contents What and Where is X11R7.5?..............................................................................................3 New OS dependent features...............................................................................................3 Configuring X for Your Hardware.....................................................................................4 Running X..............................................................................................................................5 Kernel Support for X............................................................................................................5 Rebuilding the X Distribution...........................................................................................7 Building New X Clients.......................................................................................................8 Thanks.....................................................................................................................................8 What and Where is X11R7.5? X11R7.5 is an Open Source version of the X Window System that supports several UNIX(R) and UNIX-like operating systems (such as Linux, the BSDs and Solaris x86) on Intel and other platforms. This version is compatible with X11R6.6, and is based on the XFree86 4.4.0RC2 code base, which, in turn was based on the X consortium sample implementation. See the Copyright Notice1. The sources for X11R7.5 -
Introduction to Tivoli Enterprise Data Warehouse
Front cover Introduction to Tivoli Enterprise Data Warehouse Insider’s guide to Tivoli Enterpise Data Warehouse Best practices for creating data marts Integration with all major OLAP tools Vasfi Gucer William Crane Chris Molloy Sven Schubert Roger Walker ibm.com/redbooks International Technical Support Organization Introduction to Tivoli Enterprise Data Warehouse May 2002 SG24-6607-00 Take Note! Before using this information and the product it supports, be sure to read the general information in “Notices” on page xvii. First Edition (May 2002) This edition applies to Tivoli Enterprise Data Warehouse Version 1.1. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 003 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2002. All rights reserved. Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures . .ix Tables . xv Notices . xvii Trademarks . xviii Preface . xix The team that wrote this redbook. xx Notice . xxi Comments welcome. xxii Chapter 1. Introducing building blocks. 1 1.1 Business Intelligence. 2 1.2 Business driving forces . 2 1.3 Main Business Intelligence terms . 3 1.3.1 Operational databases . 4 1.3.2 Online transaction processing (OLTP) . 4 1.3.3 Data warehouse . 5 1.3.4 Data mart . -
And It All Went Horribly Wrong: Debugging Production Systems
And It All Went Horribly Wrong: Debugging Production Systems Bryan Cantrill VP, Engineering [email protected] @bcantrill Thursday, November 17, 2011 In the beginning... Thursday, November 17, 2011 In the beginning... Sir Maurice Wilkes, 1913 - 2010 Thursday, November 17, 2011 In the beginning... “As soon as we started programming, we found to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs.” —Sir Maurice Wilkes, 1913 - 2010 Thursday, November 17, 2011 Debugging through the ages • As systems had more and more demands placed upon them, we became better at debugging their failures... • ...but as these systems were replaced (disrupted) by faster (cheaper) ones, debuggability often regressed • At the same time, software has been developed at a higher and higher layer of abstraction — and accelerated by extensive use of componentization • The high layers of abstraction have made it easer to get the system initially working (develop) — but often harder to understand it when it fails (deploy + operate) • Production systems are more complicated and less debuggable! Thursday, November 17, 2011 So how have we made it this far? • We have architected to survive component failure • We have carefully considered state — leaving tiers of the architecture stateless wherever possible • Where we have state, we have carefully considered semantics, -
Appendix A. Installation and Troubleshooting
The Almagest A-1 Appendix A. Installation and Troubleshooting Authors: Joseph T. Buck Christopher Hylands Alan Kamas Other Contributors: Stephen Edwards Edward A. Lee Kennard White A.1 Introduction This appendix consists of the following sections: • “Obtaining Ptolemy” on page A-1 discusses how to obtain Ptolemy. • “Ptolemy mailing lists and the Ptolemy newsgroup” on page A-2, discusses various forums for discussion about Ptolemy. • “Installation” on page A-3 discusses how to install Ptolemy. • “Troubleshooting” on page A-15 discusses how to find and fix problems in Ptolemy. • “Known bugs” on page A-32 lists known problems in Ptolemy. • “Additional resources” on page A-39 discusses other resources. A.2 Obtaining Ptolemy Ptolemy binaries are currently available for the following architectures: HP running HPUX10.20, Sun 4 (Sparc) running Solaris2.5.1,. In addition, Ptolemy has been compiled on SunOS4.x HPUX9.x, Linux RedHat 5.0, NetBSD_i386, IBM RS/6000 AIX4.x, SGI Irix6.x and the DEC Alpha Digital Unix 4 platforms. These additional platforms are not supported in- house and thus these ports are not tested and may not be complete. Installing the full system requires about 150 Megabytes of disk space (more if you optionally remake). The demonstration version of Ptolemy, “Ptiny,” only requires 12 Mega- bytes of disk space. All versions requires at least 8 Megabytes of physical memory. For the latest information on Ptolemy, get the Frequently Asked Questions list. Send electronic mail to [email protected] with the message: get ptolemy-hackers.FAQ in the body (not the subject) of the message. -
Enhancing Xfree86 Security
Enhancing XFree86 Security Matthieu Herrb July 2003 Libre Software Meeting Introduction Libre Software Meeting 1 What is XFree86 ? • a Free implementation of the X Window System, based on X.Org’s sample implementation (X11R6.6). • History: X386 (Three Eight Six) → XFree86 (Free Eight Six) • Runs on: Unix™, SVR4, *BSD, Linux, Windows (Cygwin), Mac OS X, etc. • Foundation for most modern GUIs and Desktops on Linux/Unix-like systems. Libre Software Meeting 2 Security concerns - summary Client side: Setuid clients Scripting toolkits Networking: connection setup / connection sniffing Server side: Server is setuid root Various issues: xdm, xfs, proxies Libre Software Meeting 3 Chapter 1 Client side security Libre Software Meeting 4 Which problems ? Traditional application level security: handling (and limiting) privileges Some remaining issues: • xterm (on systems where pty allocation needs root) • xlock like applications • ICCM and other scriptable X Toolkits and applications → out of the scope of this talk. Libre Software Meeting 5 Chapter 2 Networking issues Libre Software Meeting 6 Security at the transport level Access control done mainly at the transport level: if a client is able to get a connection to the X server, it can take full control of it: • display windows • get events • send synthetic events to other windows • change X resource database • access server-side data (atoms, pixmaps, etc) • tweak video modes Libre Software Meeting 7 X11 Transport Security models Transport types: • TCP • local (Unix domain sockets + SVR4 local) connections • SYSV SHM Authentication types: • Host based - xhost • Magic cookies - xauth • XDM • Kerberos, SUN-DES-1 (not widely used AFAIK) Too many people still use xhost + .. -
The Rise & Development of Illumos
Fork Yeah! The Rise & Development of illumos Bryan Cantrill VP, Engineering [email protected] @bcantrill WTF is illumos? • An open source descendant of OpenSolaris • ...which itself was a branch of Solaris Nevada • ...which was the name of the release after Solaris 10 • ...and was open but is now closed • ...and is itself a descendant of Solaris 2.x • ...but it can all be called “SunOS 5.x” • ...but not “SunOS 4.x” — thatʼs different • Letʼs start at (or rather, near) the beginning... SunOS: A peopleʼs history • In the early 1990s, after a painful transition to Solaris, much of the SunOS 4.x engineering talent had left • Problems compounded by the adoption of an immature SCM, the Network Software Environment (NSE) • The engineers revolted: Larry McVoy developed a much simpler variant of NSE called NSElite (ancestor to git) • Using NSElite (and later, TeamWare), Roger Faulkner, Tim Marsland, Joe Kowalski and Jeff Bonwick led a sufficiently parallelized development effort to produce Solaris 2.3, “the first version that worked” • ...but with Solaris 2.4, management took over day-to- day operations of the release, and quality slipped again Solaris 2.5: Do or die • Solaris 2.5 absolutely had to get it right — Sun had new hardware, the UltraSPARC-I, that depended on it • To assure quality, the engineers “took over,” with Bonwick installed as the gatekeeper • Bonwick granted authority to “rip it out if itʼs broken" — an early BDFL model, and a template for later generations of engineering leadership • Solaris 2.5 shipped on schedule and at quality -
Release Notes for Xfree86® 4.7.0 the Xfree86 Project, Inc August 2007
Release Notes for XFree86® 4.7.0 The XFree86 Project, Inc August 2007 Abstract This document contains information about the various features and their current sta- tus in the XFree86 4.7.0 release. 1. Introduction to the 4.x Release Series XFree86 4.0 was the first official release of the XFree86 4 series. The current release (4.7.0) is the latest in that series. The XFree86 4.x series represents a significant redesign of the XFree86 X server,with a strong focus on modularity and configurability. 2. Configuration: aQuickSynopsis Automatic configuration was introduced with XFree86 4.4.0 which makes it possible to start XFree86 without first creating a configuration file. This has been further improved in subsequent releases. If you experienced any problems with automatic configuration in a previous release, it is worth trying it again with this release. While the initial automatic configuration support was originally targeted just for Linux and the FreeBSD variants, as of 4.5.0 it also includes Solaris, NetBSD and OpenBSD support. Full support for automatic configuration is planned for other platforms in futurereleases. If you arerunning Linux, FreeBSD, NetBSD, OpenBSD, or Solaris, try Auto Configuration by run- ning: XFree86 -autoconfig If you want to customise some things afterwards, you can cut and paste the automatically gener- ated configuration from the /var/log/XFree86.0.log file into an XF86Config file and make your customisations there. If you need to customise some parts of the configuration while leav- ing others to be automatically detected, you can combine a partial static configuration with the automatically detected one by running: XFree86 -appendauto If you areusing a platform that is not currently supported, then you must try one of the older methods for getting started like "xf86cfg", which is our graphical configuration tool. -
Installation Guide Eclipse 3 / Eclipse 2
Installation Guide Eclipse 3 / Eclipse 2 Solaris ddx Version 2.2 for Solaris 2.6, 2.7 (7) and 2.8 (8) December 10, 2001 Peritek Corporation. Phone 800-281-4567 [email protected] www.peritek.com Table of Contents List of Tables...................................................................................................................................3 1 Overview.......................................................................................................................................4 1.1 Platform Support ....................................................................................................................4 1.2 Getting help ............................................................................................................................5 1.3 Using this manual...................................................................................................................5 2 Hardware Installation..................................................................................................................6 2.1 Installing the Eclipse PMC ....................................................................................................6 2.2 Installing Eclipse CPCI...........................................................................................................7 2.3 Installing Eclipse PCI.............................................................................................................7 3 Configuring the Eclipse as a Console Device.............................................................................8 -
W an in Ii D a I Ies-] W Retl N E Futui !W S Ire
' L H p i E ^ B | TwinI Falls'teacherB ftilcMs I . 'orira'newlt/luster. ' to retuiri'.ta.lo stateT.’K V i l l In steps of old rinasters.; fc : IW I ’ SIsports; 8^ ^ M liiai|ii MAGIC VAUry. D4 p Good Momiming # ■ t m 4 6 I ^ MONDAY ' # "Low: 29 H ^ November 26,20077 j Sunny and wlntf ^ 75 cents ' DtttOKOBr- ;:JL' i n i ii e s - ]N e !WS ' M atta/aOeyjxm« i ....... .. ............................ Hearing T ow i a nd a iw r e tlf u t u ii r e may decidle I ^wrhether H h ppumps go) | K d[iry in 200118 ly M H•learing e pits valleey M i g gnp-Qundwateruser;rs ; ■ j ag'Igainst fish farmeers: BjHirKattCbristesseQ TlmeiImea-Newa wrttor____________ I k ' AftAfter years of w ater squabl>lcl)les, a K hearcaring to determine thc fadate of ^ MagiJq^ c Valley’s groundwater pumimpcn - . M a m begiicgins Wednesday that could fitflnnlly sort)rt out who gets acccss to Id.'ld.-iIio|i ThThe hearing stems from call;alls by surfsjrface sprlng-water users CClear B Sprirprings Foods' Snake River Farmm niid A • < Bluelue Lakes TVout Farm. Tlic GshI farm-(: crsrs have asked thc slate to forcef grouroundwater pumpers to stop didraw- inglg Vw ater that tlie uout farms■ snysj is . theirleirs under Idalio’s ilrst-coinc.:. Ifirst* servtcrved water law, ■ ■ L j HIIM The case has a longand tumululltUQUS — —ilWlthiil 111** . blstcilstory.This spring, IdahoDcporurtm ent O M itthttitfikilM•N rtM d of.WMar 9 » a m m<san m ttw proem* 4 sn t^dfsr r»dai]daiza in|«d'M riltf tt^ y«ir ^ .,c«^ a ^UrHctttpa Tb* itste't wtHnter bo0 tt «t8 comUcr ofif VW ater Resourceal Directorr 1Dave dosing iW n , ^ ; ',■.