<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Systems on Jesse Dearing</title>
    <link>https://jesse.dev/tags/systems/</link>
    <description>Recent content in Systems on Jesse Dearing</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Sep 2016 01:11:56 -0700</lastBuildDate>
    <atom:link href="https://jesse.dev/tags/systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Who’s Running that on my System: Case of the stolen CPU</title>
      <link>https://jesse.dev/post/20160916-whos-running-that-on-my-system/</link>
      <pubDate>Fri, 16 Sep 2016 01:11:56 -0700</pubDate>
      <guid>https://jesse.dev/post/20160916-whos-running-that-on-my-system/</guid>
      <description>&lt;p&gt;Last week, I found myself needing to find what application a query was originating from.&#xA;My typical method for doing this is searching through source code before I&#xA;eventually get angry that I can’t find the query originating from an ORM and&#xA;start drafting an email decreeing that all applications get distinct logins to&#xA;the database that I’ll never send because who is going to listen anyway.&lt;/p&gt;&#xA;&lt;p&gt;I had an idea for how I can track a query all the way back to the process that&#xA;accessed it and I even scripted it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
