<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Daemon on Fran Kuo | R&amp;D Leadership</title>
    <link>https://chenfu.ai/en/tags/daemon/</link>
    <description>Recent content in Daemon on Fran Kuo | R&amp;D Leadership</description>
    <generator>Hugo -- 0.157.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Sep 2007 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://chenfu.ai/en/tags/daemon/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Practical Daemon Implementation in Embedded Linux</title>
      <link>https://chenfu.ai/en/posts/linux-daemon-implementation-embedded-systems/</link>
      <pubDate>Wed, 19 Sep 2007 00:00:00 +0000</pubDate>
      <guid>https://chenfu.ai/en/posts/linux-daemon-implementation-embedded-systems/</guid>
      <description>&lt;p&gt;For anyone working with Linux, the concept of a &amp;ldquo;Daemon&amp;rdquo; (or service) is fundamental. Daemons are background processes that operate independently of any active user session. I recently deep-dived into this topic via Devin Watson&amp;rsquo;s &lt;em&gt;Linux Daemon Writing HOWTO&lt;/em&gt;, which provides a fantastic primer and a clear template.&lt;/p&gt;
&lt;p&gt;Building on that foundation, I refactored several processes in my current project to run as persistent background services. Below is a code snippet demonstrating the core structural requirements for a Linux daemon:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
