<?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>Unix on IT Comparison</title><link>https://comparison.metacog.co.kr/tags/unix/</link><description>Recent content in Unix on IT Comparison</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 02 Aug 2026 09:26:50 +0900</lastBuildDate><atom:link href="https://comparison.metacog.co.kr/tags/unix/index.xml" rel="self" type="application/rss+xml"/><item><title>SIGTERM vs SIGKILL: Graceful vs Forced Process Termination</title><link>https://comparison.metacog.co.kr/posts/2026-08-02-sigterm-vs-sigkill-graceful-vs-forced-process-termination/</link><pubDate>Sun, 02 Aug 2026 09:26:50 +0900</pubDate><guid>https://comparison.metacog.co.kr/posts/2026-08-02-sigterm-vs-sigkill-graceful-vs-forced-process-termination/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;SIGTERM and SIGKILL are both Unix signals used to stop a running process, but they differ in whether the process gets a chance to clean up after itself. SIGTERM asks a process to terminate and lets it run its own shutdown logic, while SIGKILL is an unconditional kernel-level termination that the process cannot intercept or delay. The distinction matters for avoiding data corruption, leaked resources, and orphaned locks during shutdown.&lt;/p&gt;</description></item></channel></rss>