<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://opensource.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Greg Tinker</title>
 <link>http://opensource.sys-con.com/</link>
 <description>Latest articles from Greg Tinker</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Fri, 05 Sep 2008 01:19:21 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Linux Processes: Structure, Hangs and Core Dumps</title>
 <link>http://opensource.sys-con.com/node/244348</link>
 <description>Troubleshooting a Linux process follows the same general methodology as that used with traditional UNIX systems. In both systems, for process hangs, we identify the system resources being used by the process and attempt to identify the cause for the process to stop responding. With application core dumps, we must identify the signal for which the process terminated and proceed with acquiring a stack trace to identify system calls made by the process at the time it died. There exists neither a &#039;golden&#039; troubleshooting path nor a set of instructions that can be applied for all cases. Some conditions are much easier to solve than others, but with a good understanding of the fundamentals, a solution is not far from reach.&lt;p&gt;&lt;a href=&quot;http://opensource.sys-con.com/node/244348&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 13 Jul 2006 16:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://opensource.sys-con.com/node/244348</guid>
</item>
</channel>
</rss>
