<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Process-Management on Linux Security</title><link>https://linuxtransfer.com/tags/process-management/</link><description>Recent content in Process-Management on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 26 Jun 2026 11:11:33 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/process-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Using pgrep and pkill to Simplify Process Management and Avoid Common Mistakes with background Tasks</title><link>https://linuxtransfer.com/post/2026-06-26-using-pgrep-and-pkill-to-simplify-process-man/</link><pubDate>Fri, 26 Jun 2026 11:11:33 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-06-26-using-pgrep-and-pkill-to-simplify-process-man/</guid><description>&lt;h2 id="introduction-to-pgrep-and-pkill">Introduction to pgrep and pkill&lt;/h2>
&lt;p>When I&amp;rsquo;m managing background tasks and processes in Linux, I always reach for &lt;code>pgrep&lt;/code> and &lt;code>pkill&lt;/code>. These two commands are often overlooked, but they&amp;rsquo;re incredibly useful for searching for and managing processes by name. I&amp;rsquo;ve seen this go wrong when people use &lt;code>ps&lt;/code> with &lt;code>grep&lt;/code> - it&amp;rsquo;s just not as precise. With &lt;code>pgrep&lt;/code> and &lt;code>pkill&lt;/code>, you can avoid common mistakes when dealing with background tasks.&lt;/p></description></item></channel></rss>