Date: Thu, 16 Oct 2008 20:43:21 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 151464 for review Message-ID: <200810162043.m9GKhLVN094831@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=151464 Change 151464 by rene@rene_self on 2008/10/16 20:42:42 Section 1 of DTrace is translated (rev 1.3). Checked build. Affected files ... .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.sgml#2 edit Differences ... ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.sgml#2 (text+ko) ==== @@ -7,8 +7,11 @@ --> <!-- - The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/dtrace/chapter.sgml,v 1.1 2008/09/28 12:03:05 trhodes Exp $ + The FreeBSD Dutch Documentation Project + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/dtrace/chapter.sgml,v 1.3 2008/10/10 15:37:53 pgj Exp $ + + %SOURCE% en_US.ISO8859-1/books/handbook/dtrace/chapter.sgml + %SRCID% 1.3 --> <chapter id="dtrace"> @@ -17,74 +20,83 @@ <author> <firstname>Tom</firstname> <surname>Rhodes</surname> - <contrib>Written by </contrib> + <contrib>Geschreven door </contrib> + </author> + </authorgroup> + <authorgroup> + <author> + <firstname>René</firstname> + <surname>Ladan</surname> + <contrib>Vertaald door </contrib> </author> </authorgroup> </chapterinfo> <title>DTrace</title> - <para>DTrace, also known as Dynamic Tracing, was developed by - &sun; as a tool for locating performance bottlenecks - in production and pre-production systems. It is not, in any way, - a debugging tool, but a tool for real time system analysis to - locate performance and other issues.</para> - - <para>DTrace is a remarkable profiling tool, with an impressive - array of features for diagnosing system issues. It may also be - used to run pre-written scripts to take advantage of its - capabilities. Users may even author their own utilities using - the DTrace D Language, allowing them to customize their profiling - based on specific needs.</para> - <sect1 id="dtrace-synopsis"> - <title>Synopsis</title> + <title>Overzicht</title> <indexterm><primary>DTrace</primary></indexterm> + <indexterm> - <primary>DTrace support</primary> + <primary>DTrace-ondersteuning</primary> + <see>DTrace</see> </indexterm> - <para>After reading this chapter, you will know:</para> + <para>DTrace, ook bekend als Dynamic Tracing, was ontwikkeld door + &sun; als een gereedschap om prestatie-bottlenecks in productie- + en preproductiesystemen op te sporen. Het is in geen enkel opzicht + een debug-gereedschap, maar een gereedscahp voor real-time analyse + om prestatie- en andere zaken op te sporen.</para> + + <para>DTrace is een opmerkelijk profileringsgereedschap, met een + indrukwekkende verzameling mogelijkheden om systeemzaken te + diagnosticeren. Het kan ook worden gebruikt om vooraf geschreven + scripts te draaien om zo voordeel te halen uit de mogelijkheden. + Gebruikers kunnen zelfs hun eigen middelen schrijven door gebruik + te maken van de DTrace D Language, wat ze in staat stelt om hun + profiling aan te passen aan hun specifieke behoeften.</para> + + <para>Na het lezen van dit hoofdstuk weet u:</para> <itemizedlist> <listitem> - <para>What DTrace is and what features it provides.</para> + <para>Wat DTrace is en welke mogelijkheden het biedt.</para> </listitem> <listitem> - <para>Differences between the &solaris; DTrace implementation - and the one provided by &os;.</para> + <para>De verschillen tussen de DTrace-implementatie van + &solaris; en degene die door &os; wordt aangeboden.</para> </listitem> <listitem> - <para>How to enable and use DTrace on &os;.</para> + <para>Hoe DTrace op &os; aan te zetten en te gebruiken.</para> </listitem> </itemizedlist> - <para>Before reading this chapter, you should:</para> + <para>Voordat u dit hoofdstuk leest, dient u:</para> <itemizedlist> <listitem> - <para>Understand &unix; and &os; basics + <para>De beginselen van &unix; en &os; te begrijpen (<xref linkend="basics">).</para> </listitem> <listitem> - <para>Be familiar with - the basics of kernel configuration/compilation - (<xref linkend="kernelconfig">).</para> + <para>Bekend te zijn met de beginselen van kernelconfiguratie en + -compilatie (<xref linkend="kernelconfig">).</para> </listitem> <listitem> - <para>Have some familiarity with security and how it - pertains to &os; (<xref linkend="security">).</para> + <para>Wat bekendheid te hebben met beveiliging en hoe het zich + verhoudt tot &os; (<xref linkend="security">).</para> </listitem> <listitem> - <para>Understand how to obtain and rebuild the &os; sources - (<xref linkend="cutting-edge">).</para> + <para>Te begrijpen hoe de broncode van &os; te verkrijgen en te + herbouwen (<xref linkend="cutting-edge">).</para> </listitem> </itemizedlist> @@ -93,11 +105,12 @@ and production versions of FreeBSD with this technology. --> <warning> - <para>This feature is considered experimental. Some options - may be lacking in functionality, other parts may not work - at all. In time, this feature will be considered production - ready and this documentation will be altered to fit that - situation.</para> + <para>Deze mogelijkheid wordt als experimenteel beschouwd. Van + sommige opties kan er functionaliteit ontbreken, andere delen + kunnen in het geheel niet werken. In de loop der tijd zal deze + mogelijkheid als productierijp worden beschouwd en zal deze + documentatie worden aangepast om die situatie te + representeren.</para> </warning> </sect1> @@ -114,7 +127,7 @@ <para>There is a <literal>DDB_CTF</literal> kernel option which is used to enable support for loading the <acronym>CTF</acronym> data from kernel modules and the kernel itself. - <acronym>CTF</acronym> is the &solaris; Compressed C Type format + <acronym>CTF</acronym> is the &solaris; Compact C Type Format which encapsulates a reduced form of debugging information similar to <acronym>DWARF</acronym> and the venerable stabs. This <acronym>CTF</acronym> data is added to the binaries by the @@ -143,8 +156,7 @@ and Distribution License</literal> comes with &os;, see the <filename>/usr/src/cddl/contrib/opensolaris/OPENSOLARIS.LICENSE</filename> or view it online at - <ulink url="http://www.opensolaris.org/os/licensing">; - http://www.opensolaris.org/os/licensing</ulink>.</para>; + <ulink url="http://www.opensolaris.org/os/licensing"></ulink>.</para>; <para>This license means that a &os; kernel with the DTrace options is still <acronym>BSD</acronym> licensed; however the @@ -172,14 +184,14 @@ will be limited support for function boundary tracing.</para> </note> - <para>All sources must be rebuilt and installed with CTF options. + <para>All sources must be rebuilt and installed with <acronym>CTF</acronym> options. To accomplish this task, rebuild the &os; sources using:</para> <screen>&prompt.root; <userinput>cd /usr/src</userinput> - &prompt.root; <userinput>make WITH_CTF=1 buildworld</userinput> - &prompt.root; <userinput>make WITH_CFT=1 kernel</userinput> - &prompt.root; <userinput>make WITH_CFT=1 installworld</userinput> - &prompt.root; <userinput>mergemaster -Ui</userinput></screen> +&prompt.root; <userinput>make WITH_CTF=1 buildworld</userinput> +&prompt.root; <userinput>make WITH_CFT=1 kernel</userinput> +&prompt.root; <userinput>make WITH_CFT=1 installworld</userinput> +&prompt.root; <userinput>mergemaster -Ui</userinput></screen> <para>The system will need to be restarted.</para> @@ -194,8 +206,7 @@ <para>Finally, obtain the current DTrace toolkit. The current version is available at - <ulink url="http://www.opensolaris.org/os/community/dtrace/dtracetoolkit/">; - http://www.opensolaris.org/os/community/dtrace/dtracetoolkit/</ulink>. + <ulink url="http://www.opensolaris.org/os/community/dtrace/dtracetoolkit/"></ulink>. There is an install mechanism included; however, installation is not required to make use of the bundled utilities.</para> </sect1> @@ -260,7 +271,6 @@ will produce output similar to the following:</para> <screen>&prompt.root; <userinput>./hotkernel</userinput> -localhost# ./hotkernel Sampling... Hit Ctrl-C to end.</screen> <para>The system administrator must use the @@ -304,9 +314,7 @@ <para>This script will also work with kernel modules. To use this feature, run the script with the <option>-m</option> flag:</para> - <screen>&prompt.root; <userinput>./hotkernel -m</userinput></screen> - - <screen>localhost# <userinput>./hotkernel -m</userinput> + <screen>&prompt.root; <userinput>./hotkernel -m</userinput> Sampling... Hit Ctrl-C to end. ^C MODULE COUNT PCNT @@ -362,7 +370,7 @@ sigsuspend 6985124 read 3988049784</screen> - <para>As shown, the read system call seems to use the + <para>As shown, the <function>read()</function> system call seems to use the most time in nanoseconds with the <function>getpid()</function> system call used the least amount of time.</para> </sect1>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810162043.m9GKhLVN094831>