<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Macos on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/macos/</link>
    <description>Recent content in Macos on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 15 Aug 2017 08:41:12 -0700</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/macos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Debugging MacOS file locking with DTrace</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2017/debugging-macos-file-locks-with-dtrace/</link>
      <pubDate>Tue, 15 Aug 2017 08:41:12 -0700</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2017/debugging-macos-file-locks-with-dtrace/</guid>
      <description>A few days ago, I was stymied at work by a set of tests that had intermittent failures on OSX but not Windows.&#xA;There was a process which would try to obtain an exclusive lock on a file, using the lock-on-open provided by the BSD/MacOS O_EXLOCK flag to open(2). It also used O_NONBLOCK; if the file was locked by another process, it could be skipped. The process would hold the lock and remove (unlink(2)) the file, before close(2)-ing the descriptor.</description>
    </item>
  </channel>
</rss>
