You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ig...@apache.org on 2010/12/19 12:44:37 UTC
svn commit: r1050816 - /httpd/site/trunk/xdocs/dev/debugging.xml
Author: igalic
Date: Sun Dec 19 11:44:37 2010
New Revision: 1050816
URL: http://svn.apache.org/viewvc?rev=1050816&view=rev
Log:
Update Solaris coreadm reference, remove Apache tcpdumpscii.
Modified:
httpd/site/trunk/xdocs/dev/debugging.xml
Modified: httpd/site/trunk/xdocs/dev/debugging.xml
URL: http://svn.apache.org/viewvc/httpd/site/trunk/xdocs/dev/debugging.xml?rev=1050816&r1=1050815&r2=1050816&view=diff
==============================================================================
--- httpd/site/trunk/xdocs/dev/debugging.xml [utf-8] (original)
+++ httpd/site/trunk/xdocs/dev/debugging.xml [utf-8] Sun Dec 19 11:44:37 2010
@@ -440,7 +440,8 @@ At this point you can use:</p>
<section id="sol27">
<title>Solaris and coredumps</title>
-<p>On Solaris use <b><code>coreadm</code></b> to make
+<p>On Solaris use <a href="http://docs.sun.com/app/docs/doc/816-5166/coreadm-1m"
+><code>coreadm(1M)</code></a> to make
<code>setuid()</code> processes actually dump core. By default a setuid()
process does not dump core. This is the reason why httpd servers started as
root with child processes running as a different user (such as
@@ -452,31 +453,30 @@ directive had been set to an appropriate
<a href="#crashes">Debugging intermittent crashes</a> above.
</p>
-<p>Jens-Uwe Mager wrote:</p>
-<blockquote>
-<p><i>For example I am using:</i></p>
+<p>Example:</p>
<pre>
- # coreadm
- global core file pattern: /var/core/core.%f.%p.u%u
- init core file pattern: core
- global core dumps: enabled
- per-process core dumps: enabled
- global setid core dumps: enabled
- per-process setid core dumps: enabled
- global core dump logging: disabled
+-bash-3.00# coreadm
+ global core file pattern: /var/core/core.%f.%p.u%u
+ global core file content: default
+ init core file pattern: core
+ init core file content: default
+ global core dumps: disabled
+ per-process core dumps: enabled
+ global setid core dumps: enabled
+ per-process setid core dumps: enabled
+ global core dump logging: disabled
</pre>
-</blockquote>
</section>
<section id="tcpdump">
<title>Getting and analyzing a TCP packet trace</title>
-<p>This is more difficult than I have time to describe at the moment.
+<p>This is too deep a subject to fully describe in this documentation.
Here are some pointers to useful discussions and tools:</p>
<ul>
<li>
-snoop is a packet sniffer that is part of Solaris.
+<code>snoop</code> is a packet sniffer that is part of Solaris.
</li>
<li>
<a href="http://www.tcpdump.org/">tcpdump</a> is a packet sniffer that is
@@ -495,12 +495,5 @@ allows the analysis of the sniffed data.
another one.</li>
</ul>
-<p>There is also a simple ASCII viewer for TCP dump traces in the Apache
-repository in the file
-<code>
-<a href="http://svn.apache.org/viewvc/httpd/httpd/branches/1.3.x/src/test/tcpdumpscii.txt?view=markup">
-src/test/tcpdumpscii.txt</a></code>.</p>
-</section>
-
</body>
</document>